This chapter lists the LAN Network Manager messages you can receive when using LAN Network Manager. Messages are listed by message ID number and include an explanation of the message and suggested actions.
Messages with numbers between 1000 and 1999 are sent to LAN Network Manager from the OS/2 agent program. Refer to the documentation that is provided with the OS/2 agent for an explanation of the message and suggested actions to take to resolve the problem.
LAN Network Manager appends a "1" to the front of the message number that it receives from the OS/2 agent. Before consulting the OS/2 agent documentation, identify the appropriate message number for the OS/2 agent by removing the "1" from the number. For example, message number 1300 on LAN Network Manager corresponds to message number 300 on the OS/2 agent.
You can determine the process that generates a message by the software name given for the message in the formatted nettl log.
If you receive a message and are not able to find the message in this chapter, call IBM Service for more information. See Problem Determination for instructions on calling the IBM Technical Support center.
| 023 | Memory allocation error errno : <errnoValue>
process id : <ProcessID>
Meaning: The malloc() system call failed. The errnoValue indicates the particular error that malloc returned. The ProcessID indicates which application encountered the memory allocation error. Action: If the errnoValue is 12 (ENOMEM), ensure memory storage space has not been exhausted. If the errnoValue is 22 (EINVAL), 0 bytes were being allocated by ProcessID, contact IBM Service for more information. |
| 062 | Cannot exec the process: <Application>
Meaning: The execl() system call failed. Action: Verify the executable is in /usr/CML/bin. If it is not, reinstall LNM for AIX and retry the operation. If it is, exit the NetView for AIX graphical interface and then execute ovstop followed by ovstart. Verify all of the NetView for AIX daemons are running using ovstatus. Execute cmlstart. |
| 072 | System call connect failed: Procedure <ProcedureName>
File = <FileName>, Line = <LineNumber> Error
<errornoValue>: <errornoText>
Meaning: The connect() system call issued by a client in order to establish communication with a server has failed. This situation occurs if a client process attempts to connect with a server process and the server is not ready to accept the connection. The message is only important if attempts by the client application fail repeatedly. Action: No action required. The application will attempt to recover. If this error becomes critical, the application will issue error messages that may be used to recover. |
| 101 | Cannot open file = <file name> with access <access mode>
Meaning: Cannot open the file with the filename and access requested. Action: Ensure the file exists and has the correct access mode. |
| 102 | Cannot search directory = <directory name>
Meaning: Cannot open directory /usr/lpp/lnm/conf or one of its subdirectories. Action: Verify that the directory exists and has the correct permissions. |
| 104 | The number of records in file exceeds the limit = <maximum record
size> passed in <configuration file> with record type value =
<record
type value>
Meaning: The number of records added to the Configuration file for record type has been exceeded. Record types are:
Action: Reduce the number of records entered into the configuration file for record type so that it does not exceed the limit. |
| 201 | <Application name>: Cannot open LNM for AIX configuration
file <Filename>
Meaning: cmld could not open the cmld.conf file in /usr/CML/conf directory. Action: Check the file for read access permission. If the file does not exist, either installation failed or the file has been deleted by accident. Reinstall LAN Network Manager. |
| 202 | <Application name>: Syntax error in LNM for AIX configuration
file <Filename>
Meaning: The configuration file specified is corrupted. Action: Reinstall LAN Network Manager. |
| 203 | <Application name>: System call socket() failed
Meaning: The system call socket() failed. Action: After exiting the NetView for AIX graphical interface, stop LNM for AIX. Then execute ovstop followed by ovstart. Use ovstatus to verify the NetView for AIX daemons are running. Restart LNM for AIX. |
| 204 | <Application name>: System call bind() failed
Meaning: The system call bind() failed. Action: After exiting the NetView for AIX graphical interface, stop LNM for AIX. Then execute ovstop followed by ovstart. Use ovstatus to verify the NetView for AIX daemons are running. Restart LNM for AIX. |
| 205 | <Application name>: System call select() failed
Meaning: The system call select() failed. Action: After exiting the NetView for AIX graphical interface, stop LNM for AIX. Then execute ovstop followed by ovstart. Use ovstatus to verify the NetView for AIX daemons are running. Restart LNM for AIX. |
| 206 | <Application name>: System call accept() failed
Meaning: The system call accept() failed. Action: After exiting the NetView for AIX graphical interface, stop LNM for AIX. Then execute ovstop followed by ovstart. Use ovstatus to verify the NetView for AIX daemons are running. Restart LNM for AIX. |
| 207 | <Application name>: Invalid parameter
Meaning: The parameter on the LNM for AIX service interface command is not valid. Action: Correct and retry the command again. |
| 208 | <Application name>: Invalid parameter count
Meaning: Invalid number of parameters on the LNM for AIX service interface command. Action: Correct and retry the command again. |
| 209 | Host name size exceeded.
Meaning: An invalid hostname was configured on the LNM for AIX service interface command (SMIT). Action: Correct the hostname. |
| 210 | <Application name>: cmld is not running, use ovstart
cmld to start cmld
Meaning: LNM for AIX daemon cmld is not running. Action: Verify that the NetView for AIX daemons are running using ovstatus. Use ovstart cmld to start cmld. |
| 212 | <Application name>: Your trial period has expired. To
order, please contact your IBM Representative.
Meaning: The trial period for LNM for AIX has expired. Action: To purchase an LNM for AIX license, please contact your IBM Representative. |
| 216 | usage: cmlstart [clear]
Meaning: The parameters on the cmlstart command are not valid. Action: Refer to the man page for usage. |
| 217 | usage: cml_agent_found [Object ID] [IP Address]
Meaning: The parameters on the cml_agent_found command are not valid. Action: Refer to the man page for usage. |
| 218 | usage: cml_agent_remove [Object ID][IP Address]
Meaning: The parameters on the cml_agent_remove command are not valid. Action: Refer to the man page for usage. |
| 219 | usage: cmlstop [clear]
Meaning: The parameters on the cmlstop command are not valid. Action: Refer to the man page for usage. |
| 259 | <application> Timeout waiting for applications to start.
Meaning: A cmlstart command was requested, but the application did not acknowledge the start. Action: This may not be an error if the system is running slowly. Use the cmlstatus command to see the current status of the application. |
| 260 | <application> Timeout waiting for agent to be found.
Meaning: A cml_agent_found command was requested, but the agent did not respond before the timeout. Action: This error is usually caused by a communication error with the agent. Verify the following:
|
| 261 | <application> Timeout waiting for agent to be deleted.
Meaning: A cml_agent_delete command was requested, but the application did not respond before the timeout. Action: This may not be an error if the system is running slowly. Use the cmlstatus command to see the current status of the application. |
| 262 | Topology initialization failed.
Meaning: lnmtopod failed to start. Action: Verify that nvot_server is running by issuing the ovstatus command. If nvot_server is not running, issue the ovstart nvot_server command. If nvot_server fails to start, format the NetView for AIX nettl log and look for nvot_server error messages. See the NetView for AIX documentation for instructions on formatting the nettl log "/usr/OV/bin/netfmt -f /usr/OV/log/nettl.LOG00". |
| 263 | Discovery initialization failed.
Meaning: cmldiscd failed to start. Action: No other daemons will start until the problems with the cmldiscd daemon are fixed. Format the nettl log and look for messages for the cmldisc daemon. The following command should format the NetView for AIX nettl log: "/usr/OV/bin/netfmt -f /usr/OV/log/nettl.LOG00". See the NetView for AIX documentation for information about formatting the nettl log. |
| 264 | <application> Timeout waiting for agent to be added.
Meaning: A cml_agent_add command was requested, but the agent did not respond before the timeout. Action: This error is usually caused by a communication error with the agent. Verify the following:
|
| 265 | <agent> Timeout waiting for agent to be removed.
Meaning: A cml_agent_remove command was requested, but the application did not respond before the timeout. Action: This may not be an error if the system is running slowly. Use the cmlstatus command to see the current status of the application. |
| 266 | <agent> There is no running capability interested in the
agent_ID(s).
Meaning: An agent with an agent_ID (sysObjectID/MIB variable) was requested to be discovered, but there is no running application managing this type of agent. Action: Make sure there is an application installed and running that manages this type of agent. Use the cmlstatus command to query the installed and running applications. |
| 269 | Discovery application is not running.
Meaning: The cmldiscd daemon is not running. Action: Issue the ovstatus command to make sure all the NetView for AIX daemons are running properly. Once all the NetView for AIX daemons are running properly, issue the restart command to restart the desired applications. If applications do not start properly, format the nettl log and check for errors. The following command should format the NetView for AIX nettl log: "/usr/OV/bin/netfmt -f /usr/OV/log/nettl.LOG00". See the NetView for AIX documentation for information about formatting the nettl log. |
| 270 | Capability was not started because it depended on <application>
capability.
Meaning: The requested application cannot be started until the required application is started. Action: Start the required application. |
| 271 | nvot_server CONNECTION ERROR
Meaning: The nvot_server connection failed. Make sure nvot_server is running. Action: Verify that nvot_server is running by issuing the ovstatus command. If nvot_server is not running, issue the ovstart nvot_server command. If nvot_server fails to start, format the NetView for AIX nettl log and look for nvot_server error messages. See the NetView for AIX doc for instructions on formatting the nettl log "/usr/OV/bin/netfmt -f /usr/OV/log/nettl.LOG00". |
| 272 | nvot_server DATABASE ERROR
Meaning: The nvot_server connection failed. Make sure nvot_server is running. Action: Verify that nvot_server is running by issuing the ovstatus command. If nvot_server is not running, issue the ovstart nvot_server command. If nvot_server fails to start, format the NetView for AIX nettl log and look for nvot_server error messages. See the NetView for AIX documentation for instructions on formatting the nettl log "/usr/OV/bin/netfmt -f /usr/OV/log/nettl.LOG00". |
| 273 | Symbols Manager connection error.
Meaning: cmld could not connect to Symbols Manger. The device will not be changed to executable in the NetView for AIX maps. Action: Restart ovw and check the nettl logs. Issue the following command to format the NetView for AIX nettl log: "/usr/OV/bin/netfmt -f /usr/OV/log/nettl.LOG00" See the NetView for AIX documentatio for information about formatting the nettl log. |
| 275 | Symbols Manager Server error.
Meaning: cmld may have lost connection to the Symbols Manger. Some devices may not be changed to executable in the NetView for AIX maps. Action: Restart ovw and check the nettl logs. The following command should format the NetView for AIX nettl log: "/usr/OV/bin/netfmt -f /usr/OV/log/nettl.LOG00" See the NetView for AIX documentation for information about formatting the nettl log. |
| 276 | Unexpected error on capability start: <application>.
Meaning: A cmlstart command was requested for the application and the application did not acknowledge the start. Action: Use SMIT to verify that the requested application is installed. If the application is installed, use cmlstatus to determine the status of the application. |
| 277 | Unexpected error on capability stop: <application>.
Meaning: A cmlstop command was requested for the application and the application did not acknowledge the stop. Action: Use SMIT to verify that the requested application is installed. If the application is installed, use the cmlstatus command to determine the status of the application. |
| 301 | Change label request received for a non-existent resource. graph
Protocol = <protocol> graph Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services to change a label for a resource that is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 302 | Change label request received for a non-existent element. vertex
Protocol = <protocol> vertex Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services to change a label for a resource that is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 305 | Insert request received for a non-existent resource. graph
Protocol
= <protocol> graph Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services to add a resource to a segment, but the resource is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 306 | Insert request received for a non-existent upstream neighbor.
graph
Protocol = <protocol> graph Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services to add a resource downstream from a resource that is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 307 | Insert request received for a non-existent downstream neighbor.
Meaning: An LAN Network Manager application has asked Topology Services to add a resource upstream from a resource that is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 308 | Associate request received for a non-existent device. Device
Protocol
= <protocol> Device Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services to add an existing resource to a graph, but the resource is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 314 | Associate request received for a non-existent element. parent
Protocol
= <protocol> parent Name = <name> component Protocol =
<protocol>
component Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services to add an existing element to a graph, but the resource is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 315 | Associate request received for a non-existent parent. parent
Protocol
= <protocol> parent Name = <name> component Protocol =
<protocol>
component Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services to add a resource to a view that is not in the Topology Services cache. This means that a device or network has been has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 316 | Change extension request received for a non-existent resource.
graph
Protocol = <protocol> graph Name = <name>
Meaning: Topology Services received a request for a resource that is not in its cache. That means that the resource has been discovered but is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 317 | Change extension request received for a non-existent element.
vertex
Protocol = <protocol> vertex Name = <name>
Meaning: Topology Services received a request for an element that is not in its cache. That means that the resource has been discovered but is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 320 | Change status request received for a non-existent element.
Element
Protocol = <protocol> Element Name = <name>
Meaning: Topology Services received a request for an element that is not in its cache. That means that the resource has been discovered but is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 322 | Change status request received for a non-existent arc.
aEndpointName
= <name> zEndpointName = <name>
Meaning: Topology Services received a request for an arc that is not in its cache. That means that the arc has been discovered but is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 324 | Change status request received for a non-existent resource.
Resource
Protocol = <protocol> Resource Name = <name>
Meaning: Topology Services received a request for a resource that is not in its cache. That means that the resource has been discovered but is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 326 | Change status request received for a non-existent view. graph
Name
= <name>
Meaning: An LAN Network Manager application has asked Topology Services to change a view that is not in the Topology Services cache. This means that a segment or network has been has been discovered that is not in any other view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 327 | Change status request received for a non-existent arcs in view.
graph Protocol = <protocol> graph Name = <name>
Meaning: Topology Services received a request for an arc that is not in its cache. That means that the arc has been discovered but is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 329 | Change contents request received for a non-existent view. View
Protocol
= <protocol> View Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services change a view that is not in the Topology Services cache. This means that a view has been discovered by the application but is not known to Topology Services. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 330 | Change contents request received for a non-existent device.
Resource
Protocol = <protocol> Resource Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services change a device that is not in the Topology Services cache. This means that a device has been discovered by the application but is not known to Topology Services. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 331 | Change type request received for a non-existent resource. graph
Protocol = <protocol> graph Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services change a resource that is not in the Topology Services cache. This means that a resource has been discovered by the application but is not known to Topology Services. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 332 | Change type request received for a non-existent element. vertex
Protocol = <protocol> vertex Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services change an element that is not in the Topology Services cache. This means that an element has been discovered by the application but is not known to Topology Services. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 339 | Create arc request received for a non-existent endpoints.
aEndpointProtocol
= <protocol> aEndpointName = <name> zEndpointProtocol =
<protocol>
zEndpointName = <name>
Meaning: An LAN Network Manager application has asked Topology Services to create an arc between endpoints that are not in the Topology Services cache. This means that the endpoints have been discovered but are not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 340 | Delete request received for a non-existent view. graph Name =
<name>
Meaning: An LAN Network Manager application has asked Topology Services to delete a view that is not in the Topology Services cache. This means that a segment or network has been has been discovered that is not in any other view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 341 | Delete request received for a non-existent arc. aEndpointName =
<name>
zEndpointName = <name>
Meaning: Topology Services received a request for an arc that is not in its cache. That means that the arc has been discovered but is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 342 | Delete request received for a non-existent resource. graph Name
= <name>
Meaning: An LAN Network Manager application has asked Topology Services delete a resource that is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 343 | Delete request received for a non-existent element. vertexName =
<name>
Meaning: An LAN Network Manager application has asked Topology Services change an element that is not in the Topology Services cache. This means that an element has been discovered by the application but is not known to Topology Services. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 346 | Root not found when executing delete Protocol. Database is
empty.
Meaning: Topology Services cannot find the LAN Network Manager for AIX graph in the NetView for AIX database. Therefore, it cannot look for the children of that graph and delete the ones that match the requested protocol. Action: None. |
| 347 | Remove request received for a non-existent resource. graph
Protocol
= <protocol> graph Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services remove a resource that is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 348 | Remove request received for a non-existent downstream neighbor.
Meaning: An LAN Network Manager application has asked Topology Services remove a resource from a segment, but the downstream neighbor of the resource is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 349 | Remove request received for a non-existent upstream neighbor.
Meaning: An LAN Network Manager for AIX application has asked Topology Services remove a resource from a segment, but the upstream neighbor of the resource is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 350 | Connection with Topology already established.
Meaning: An LAN Network Manager for AIX application has attempted to establish communications with Topology Services, even though it has already successfully done so. Action: No response is required. |
| 351 | Connection with Topology was not established.
Meaning: Topology Services tried to establish a connection with the cmld daemon, but was unsuccessful. Action: After exiting the NetView for AIX graphical interface, stop LNM for AIX. Then execute ovstop followed by ovstart. Use ovstatus to verify the NetView for AIX daemons are running. Restart LNM for AIX. |
| 386 | View not found when executing getPosition.
Meaning: Topology Services cannot find the information it expects in its database. Action: Go to the directory /usr/CML/databases. Verify that the files lnmTopoGraph.spec and lnmTopoVertex.spec are present and have not been changed since your last installation of LAN Network Manager for AIX. If they have been changed, reinstall LAN Network Manager. Otherwise, contact IBM Service for more information. |
| 387 | Element not found when executing getPosition.
Meaning: Topology Services cannot find information it expects in its database. Action: Go to the directory /usr/CML/databases. Verify that the files lnmTopoGraph.spec and lnmTopoVertex.spec are present and have not been changed since your last installation of LAN Network Manager for AIX. If they have been changed, reinstall LAN Network Manager. Otherwise, contact IBM Service for more information. |
| 388 | Port not found when executing getPosition.
Meaning: Topology Services cannot find information it expects in its database. Action: Go to the directory /usr/CML/databases. Verify that the files lnmTopoGraph.spec and lnmTopoVertex.spec are present and have not been changed since your last installation of LAN Network Manager for AIX. If they have been changed, reinstall LAN Network Manager. Otherwise, contact IBM Service for more information. |
| 389 | Device not found when executing getPosition.
Meaning: Topology Services cannot find information it expects in its database. Action: Go to the directory /usr/CML/databases. Verify that the files lnmTopoGraph.spec and lnmTopoVertex.spec are present and have not been changed since your last installation of LAN Network Manager for AIX. If they have been changed, reinstall LAN Network Manager. Otherwise, contact IBM Service for more information. |
| 393 | Root not found when executing timeoutReceived. Database is
empty.
Meaning: Topology Services was unable to retrieve its top-level view from the NetView for AIX Generic Topology Database. Action: Shut down LAN Network Manager for AIX. Use SMIT to clear the database. (Maintain...Clear LNM for AIX databases). Restart LAN Network Manager for AIX. If the problem persists, contact IBM Service for more information. |
| 394 | Trap send error when executing changeMemberPosition. graph Name
= <name> Reason Code = <code>
Meaning: There was a problem with a message sent by Topology Services to NetView for AIX. Action: Ensure the NetView for AIX daemons nvot_server or ovwdb are still running, using the ovstatus command. If they are not, restart them. If the problem persists, save the nettl log and contact IBM Service for more information. |
| 395 | Unknown message received by TopologyServer.
Meaning: An LAN Network Manager for AIX application sent Topology Services a request using a request identifier that is unsupported. Action: None, although you may want to resynchronize any critical views since a message may have been corrupted and thus lost. If the problem persists, save the nettl log and contact IBM Service for more information. |
| 396 | Graph spec file was not opened.
Meaning: Topology Services cannot find information it expects in its database. Action: Go to the directory /usr/CML/databases. Verify that the file lnmTopoGraph.spec is:
Add the read permission if it is not there. If the file is missing or changed, reinstall LAN Network Manager. |
| 397 | Arc spec file was not opened.
Meaning: Topology Services cannot find information it expects in its database. Action: Go to the directory /usr/CML/databases. Verify that the file lnmTopoArc.spec is:
Add the read permission if it is not there. If the file is missing or changed, reinstall LAN Network Manager. |
| 398 | Vertex spec file was not opened.
Meaning: Topology Services cannot find information it expects in its database. Action: Go to the directory /usr/CML/databases. Verify that the file lnmTopoVertex.spec is:
Add the read permission if it is not there. If the file is missing or changed, reinstall LAN Network Manager. |
| 399 | getGraphType request received for a non-existent graph. graphName
= <name>
Meaning: An LAN Network Manager application has asked Topology Services to act on a graph that is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 400 | getVertexType request received for a non-existent vertex.
vertexName
= <name>
Meaning: An LAN Network Manager application has asked Topology Services to act on a graph that is not in the Topology Services cache. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 410 | Error in initialization process (could not create root graph).
Meaning: There was a problem with a message sent by Topology Services to NetView for AIX. Action: Ensure the NetView for AIX daemons nvot_server or ovwdb are still running, using the ovstatus command. If they are not, restart them. Stop any running LNM for AIX monitoring daemons. Restart LNM for AIX. If the problem remains, stop any running LNM for AIX monitoring daemons. Use SMIT to clear the database. (Maintain...Clear LNM for AIX databases). Restart LNM for AIX. If the problem still persists, save the nettl log and contact IBM Service for more information. |
| 418 | Topology config file not found, default values will be used.
Meaning: The file that would contain any user-defined Topology Services customization was not found. Action: None. This is an expected message, if no customization has been done of General Configuration Parameters using SMIT. |
| 419 | Topology config file empty, default values will be used.
Meaning: The file that would contain any user-defined Topology Services customization is empty. Action: None. However, the General Configuration Parameters customization has been lost. Reenter it using SMIT. |
| 424 | SNMP error -- OVsnmpErrno: <number>, nvSnmpErrno:
<number>,
nvSnmpSubsys: <subsystem>
Meaning: Topology Services failed in an attempt to open a session with NetView for AIX to send a trap. Action: Look at the man page for OVsnmpOpen. The error codes should help you determine the correct action to take. If they do not, then shut down and restart LAN Network Manager for AIX and NetView for AIX. If the problem persists, contact IBM Service for more information. |
| 425 | Unable to close SNMP session -- OVsnmpErrno: <error number>
Meaning: Topology Services failed in an attempt to close a trap session with NetView for AIX. Action: Look at the man page for OVsnmpClose. The error number should help you determine the correct action to take. If it does not, then shut down and restart LAN Network Manager for AIX and NetView for AIX. If the problem persists, contact IBM Service for more information. |
| 426 | Unable to create trap -- OVsnmpErrno: <error number>
Meaning: Topology Services failed in an attempt to build a trap to send to NetView for AIX. Action: Look at the man page for OVsnmpCreatePdu. The error number should help you determine the correct action to take. If it does not, then shut down and restart LAN Network Manager for AIX and NetView for AIX. If the problem persists, contact IBM Service for more information. |
| 427 | Unable to send trap -- OVsnmpErrno: <error number>
Meaning: Topology Services failed in an attempt to send a trap to NetView for AIX. Action: Look at the man page for OVsnmpSend. The error number should help you determine the correct action to take. If it does not, then shut down and restart LAN Network Manager for AIX and NetView for AIX. If the problem persists, contact IBM Service for more information. |
| 430 | Disassociate request received for a non-existent component.
parent
Protocol = <protocol> parent Name = <name> graph Protocol =
<protocol>
graph Name = <name>
Meaning: Topology Services is trying to remove a resource from a graph, but the Topology Services cache has no record that the resource is in the graph. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 431 | Disassociate request received for a non-existent parent. parent
Protocol = <protocol> parent Name = <name> graph Protocol =
<protocol>
graph Name = <name>
Meaning: An LAN Network Manager for AIX application as asked Topology Services to remove a resource from a graph, but the Topology Services cache has no record of the graph. This means a resource has been discovered that is not in any view. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 432 | Disassociate request received for a non-existent element. parent
Protocol = <protocol> parent Name = <name> vertex Protocol =
<protocol>
vertex Name = <name>
Meaning: An LAN Network Manager application has asked Topology Services change an element is not in the Topology Services cache. This means that an element has been discovered by the application but is not known to Topology Services. Action: This problem should be resolved the next time the application resynchronizes a view that contains the resource. To resolve it more quickly, you can manually resynchronize the view if you know which one the resource should have been in. |
| 435 | Cannot get ID for field <resource name> from OVw. OVw error
is: <NV/6K error message>.
Meaning: The Topology Services application was unable to get an object's resource ID from NetView/6000 database. Action: Stop any LNM for AIX monitoring daemons. Exit the NetView for AIX graphical interface. Execute ovstop, then ovstart. Use ovstatus to verify that the NetView for AIX daemons are running. Restart LNM for AIX. If the problem remains, stop any running LNM for AIX monitoring daemons. Use SMIT to clear the database. (Maintain...Clear LNM for AIX databases). Restart LNM for AIX. If the problem still persists, save the nettl log and contact IBM Service for more information. |
| 436 | Cannot get value for field <field name> from OVw. OVw error
is: <NetView/6000 error message>.
Meaning: The Topology Services application was unable to get an object's field name from NetView/6000 database. Action: Stop any LNM for AIX monitoring daemons. Exit the NetView for AIX graphical interface. Execute ovstop, then ovstart. Use ovstatus to verify that the NetView for AIX daemons are running. Restart LNM for AIX. If the problem remains, stop any running LNM for AIX monitoring daemons. Use SMIT to clear the database. (Maintain...Clear LNM for AIX databases). Restart LNM for AIX. If the problem still persists, save the nettl log and contact IBM Service for more information. |
| 446 | Topology clients failed to close socket at shutdown.
Meaning: One or more LAN Network Manager application did not close the connection with topology at shut down. Action: None. |
| 448 | Topology index cache corrupted. file: <file name>
line: <line
number>
Meaning: Internal topology database of LAN Network Manager has been corrupted. Action: Clear the NetView for AIX databases using the NetView for AIX SMIT option (Maintain...Clear databases). Then stop LAN Network Manager using the clear option and restart. |
| 452 | Cannot open Window Description File: < PDF filename >.
Meaning: The PDF file cannot be opened or does not exist. Action: Verify that the .pdf files are installed in /usr/CML/databases directory and if the permissions are properly setup. If .pdf files are not installed, reinstall LAN Network Manager. |
| 454 | OVw initialization error
Meaning: During EUI Initialization, an OVw initialization error was returned. Action: Verify that the AIX NetView/6000 graphical interface processes are running. Once all of these are running, retry accessing the management window. If the problem persists, contact IBM Service for more information. |
| 455 | Error while registering action callback.
Meaning: During EUI Initialization, an error occurred while registering the OVw action callbacks. The probable cause is that OVw actions which are being registered do not match the ones described in registration file. Action: Verify that the AIX NetView/6000 graphical interface processes are running. Once all of these are running, retry accessing the management window. If the problem persists, contact IBM Service for more information. |
| 456 | Error while registering termination callback.
Meaning: During EUI Initialization, an error occurred while registering the OVw termination callback. Action: Verify that the AIX NetView/6000 graphical interface processes are running. Once all of these are running, retry accessing the management window. If the problem persists, contact IBM Service for more information. |
| 469 | OVW not running.
Meaning: EUI was initialized before starting OVw. Action: Start the AIX NetView/6000 graphical interface. |
| 501 | Error <errorCode> from agent in <routine>,
RN=<resourceName>
Meaning: An SNMP response was received in the specified routine with an unexpected SNMP error code while building the object with the given resource name. Action: The following table describes the possible error codes and responses to them:
|
| 502 | Segment resynchronized due to timeout in <routine>,
RN=<resourceName>
Meaning: An SNMP response was not received in the specified routine within the time specified in the NetView for AIX SNMP configuration while building the object with the given resource name. This could be caused by a network connection problem, or a device problem. Action: If this message persists, physically verify that the device in question is functional. If so, extend the timeout value in the NetView for AIX SNMP Configuration window. |
| 503 | Segment resynchronized due to trap <trapName> in <routine>
Meaning: The following FDDI traps can cause a segment to be resynchronized:
Also, the following generic traps will cause a resync:
This message indicates that the specified trap was received in the given routine. Action: None. |
| 504 | SNMP retry count exceeded in <routine>, RN=<resourceName>
Meaning: This message is generated when more than 10 timeouts are received while attempting to issue SNMP requests against an FDDI object with the given resource name in the specified routine. Action: If this message persists, physically verify that the device in question is functional. If so, increase the timeout value in the NetView for AIX SNMP Configuration window. |
| 505 | Error <errorNumber> from topology in <routine>,
RN=<resourceName>
Meaning: Error errorNumber occurred while communicating with lnmtopod in routine while building an object with the given resource name. Action: Issue the cmlstatus command to verify that lnmtopod is running. If it is not, check the nettl log to determine the cause of the error. Then reissue cmlstart to restart the application. |
| 507 | Memory allocation failed in <routine> getting <dataType>
Meaning: A memory allocation error has occurred in routine while trying to allocate memory for the given data type. This usually indicates a shortage of hardware resources. Action: In the short term, shut down some other applications, then restart LAN Network Manager. In the long term, obtain more memory. |
| 508 | The Socket to <application> failed in <routine> with
rc = <returnCode>
Meaning: A socket failure has occurred in the specified routine while communicating with one of the applications listed below. Action:
|
| 509 | Unexpected Case in <routine>. Case number = <value>,
RN = <resourceName>
Meaning: While building the object specified by resource name, in the specified routine, an unexpected value was encountered. This can occur in an <object>::processingResponse method. In these cases, this indicates a device that may not support SMT properly. In any other situation, this probably represents a programming error. Action: If this falls under the programming error category, contact IBM service. |
| 512 | No <object> Found in <routine>, RN = <resourceName>,
type = <type>
Meaning: This message indicates failure to find an object. Action: None. If the problem persists, contact IBM service. |
| 515 | Frame error unknown in <routine>, value =
<frameErrorFlagValue>,
RN = <resourceName>
Meaning: The macFrameErrorFlag value received in routine while building object resourceName is unexpected. This could indicate the following condition:
Action: None. |
| 516 | Validity flag false for <variable> in <routine>, RN =
<resourceName>
Meaning: While processing the specified variable for object resourceName, a validity flag with value false was received. Action: None. |
| 517 | Configuration file missing. IPAddress = <ipAddress>
Meaning: There is no configuration file for the agent with this IP address. Action: If desired, create a configuration file using SMIT CML. |
| 518 | Panel requested resynch. IPAddress = <ipAddress>
Meaning: A resynchronize request was received from lnmfddimgr for the agent with the specified IP address. Action: None. |
| 519 | Trap Correlation failed. rc = <returnCode>, OVsnmpErrno =
<errorNumber>,
Error String = <errorString>, Specific = <specificTrapNumber>,
Generic = <genericTrapNumber>
Meaning: An error occurred while trying to send a correlation trap to NetView for AIX. Action: Issue ovstart to ensure that all NetView for AIX processes are running. |
| 520 | Unexpected Trap in <routine>. Generic number =
<genericTrapNumber>,
specific Number = <specificTrapNumber>, RN = <resourceName>
Meaning: A generic trap other than warmStart, coldStart, or linkUp was received from an FDDI Proxy Agent station. Action: None. |
| 521 | The Control program has terminated. The FDDI application will
terminate.
<routine>
Meaning: The cmld daemon is required for LAN Network Manager to run. Action: Restart LAN Network Manager using the cmlstart command. |
| 522 | The Management Application has terminated. <routine>
Meaning: lnmfddimgr has terminated. Action: Restart it by selecting a FDDI object and requesting a window. |
| 523 | Agent in Agent Found already exists: <ipAddress>
Meaning: A duplicate agent found message was received. Action: None. |
| 524 | FDDI discovery application terminated
Meaning: lnmfddimon terminated. Action: Restart with cmlstart. If problem persists, contact IBM Service for more information. |
| 527 | Agent in Agent Delete does not exist: <ipAddress>
Meaning: The agent to be deleted cannot be found. Action: None. |
| 551 | <objectType> action FAILED due to
<snmpFailureReasonText>.
Meaning: An SNMP action for objectType failed for the reason given in the SNMP error text. Action: The following table describes the possible error codes and responses to them:
|
| 552 | <objectType> action completed successfully.
Meaning: Command completed successfully. Action: None. |
| 553 | Add Window failed. rc = <returnCode> in
<routine>.
Meaning: An error occurred while creating a new window. Action: This is an out-of-resources error. Close one or more windows and retry the operation. |
| 556 | Error accessing config file.
Meaning: An error occurred trying to access the config file. Action: This probably indicates that NetView for AIX was started without root privileges. Restart NetView for AIX with root privileges. |
| 557 | Unexpected Case in <routine>. Case number =
<receivedValue>,
Instance = <panelID>.
Meaning: While building the window specified by the instance, in the specified routine, an unexpected value was encountered. Action: This can indicate one of two things:
|
| 558 | lnmfddimon is not running.
Meaning: The LAN Network Manager FDDI discovery application is not running. Action: Restart LAN Network Manager. |
| 559 | lnmfddimon socket is inactive.
Meaning: The socket used for communication between the FDDI discovery and management applications is not active, probably because lnmfddimon has not been started. Action: Restart LAN Network Manager. |
| 560 | lnmfddimon socket has failed.
Meaning: The socket used for communication between the FDDI discovery and management applications has become inactive, probably because lnmfddimon has stopped. Action: Restart LAN Network Manager. |
| 561 | Error <returnCode> from euiInit in <routine>.
Meaning: An error occurred while initializing the EUI library. Action: Retry the operation. Consult the nettl log for a message corresponding to the return code. If the error persists, contact IBM service. |
| 562 | Set attribute failed in <routine> with rc =
<returnCode>.
Meaning: An error occurred trying to directly set a window attribute, outside the normal get/set operation scope. Action: Consult the nettl log for a message corresponding to the return code. If the error persists, contact IBM service. |
| 563 | Agent indices reassigned - panels may no longer correspond to expected
objects. It is suggested that all open windows be closed and
reopened.
Meaning: Due to an index reassigned trap from the FDDI agent, the indices of the SMT objects have been reassigned. Consequently, the currently open windows may no longer correspond to the objects they were opened against. Action: Close and reopen all currently open windows. |
| 564 | Invalid panel. id = <panelID> in <routine>.
Meaning: A callback was received from OVw for which there is no corresponding window. This could indicate that the registration file has been altered. Action: Reinstall LAN Network Manager. If the problem persists, contact IBM service. |
| 565 | Memory allocation failed in <routine>.
Meaning: A fault occurred when the application tried to allocate memory. Action: Free resources by terminating unneeded applications. Alternatively, install more memory in the affected workstation. |
| 569 | Resynchronize performed - panels may no longer correspond to expected
objects. It is suggested that all open windows be closed and
reopened.
Meaning: Due to resynchronize (due either to a request or timer pop), the indices of the SMT objects have been reassigned. Consequently, the currently open windows may no longer correspond to the objects they were opened against. Action: Close and reopen all currently open windows. |
| 570 | Resynchronize request has been sent to lnmfddimon.
Meaning: The resynchronize request has been transmitted to lnmfddimon. Action: None. |
| 573 | The Socket to <applicationName> failed in <routine> with
rc = <returnCode>.
Meaning: The socket used for communication between the FDDI discovery and management applications has become inactive, probably because lnmfddimon has stopped. Action: Restart lnmfddimon using the cmlstart command. |
| 574 | Stopping lnmfddimgr.
Meaning: lnmfddimgr is stopping due to stoppage of OVw. Action: None. |
| 601 | Unexpected value <value> in switch statement in procedure
<procedure
name> Buffer contents = <buffer contents>
Meaning: The data does not conform to the expected set. Action: In general this indicates a programming error. If it does not reoccur it can be due to a failure in the transmission of data on the socket. If it reoccurs, contact IBM Service for more information. |
| 602 | NAUN change processing failed on segment <segment number> for
station <adapter address> NAUN <adapter address>.
Meaning: One or more NAUN change traps have been lost. The current trap does not fit the expected pattern for stations going offline or coming online. Action: If this occurs for only one segment, manually resynchronize the segment. If it occurs for multiple segments for the same LNM OS/2 Agent, manually resynchronize the agent. This may occur in conjunction with message 613 for the OVsnmp Receiving session. You may reduce the number of times this occurs by increasing the size of the receiving buffer for the TCP/UDP socket for trapd. |
| 603 | Authentication failure for <IP address>.
Meaning: An SNMP generic trap 4 was received. Action: Verify that
|
| 604 | Socket connection not yet established from <name of executable>
to <name of executable>.
Meaning: The LNM OS/2 Agent discovery application (lnmlnmemon) must be able to communicate with each of the following executables: lnmtopod, cmld, lnmBaseTimer, lnmlnmeint. If it cannot establish communications, it will continue to attempt to do so, writing this message to the log every two minutes. There may be additional messages which indicate why the socket connections cannot be established. Action: The speed of the RISC and its workload may cause this situation to occur and be resolved without any action. If the log is being flooded with these messages, stop LNM for AIX. Use the nettl log and cmlstatus to determine why determine why one or more of the executables is not running. If possible correct the problem and restart LNM for AIX. Otherwise contact IBM Service for more information. |
| 605 | View Built for resource <resource identifier>
Meaning: This message indicates that the LNM OS/2 Agent discovery application has completed discovery of the resource named in the message. The resource identifier will either be for an agent or a segment. This does not imply that all resources attached to the resource identified were successfully discovered. Only that the LNM OS/2 Agent discovery application is not attempting to determine the resource configuration at this time. Action: None. |
| 606 | Duplicate start message received
Meaning: The LNM OS/2 Agent discovery application initially comes up and waits for the control program to tell it to run. This is done with a start message. If this occurs more than once, the additional requests are discarded but noted in the log. Action: None. |
| 607 | Request for unknown resource <resource identifier>.
Meaning: The LNM OS/2 Agent discovery application expects to be able to match the resource requested to a resource known in its internal data storage. Action: This message occurs if an attempt is made to remove an agent that is not currently known to the LNM OS/2 Agent discovery application. In this case, verify that the parameters entered with cml_agent_remove are correct. If they are correct, verify that the agent has been discovered during the current LNM for AIX session. It is not possible to remove the agent representation from the display using this command unless the agent was discovered during this session. If the intent is to remove the agent from the display, execute an cml_agent_found followed by cml_agent_remove. This message also occurs if the LNM OS/2 Agent management application requests information about a resource not currently known to the LNM OS/2 Agent discovery application. This may occur if the request occurs during a resynchronize or if the request occurs and the agent was not discovered during this session. If the agent has not been discovered, execute an cml_agent_found and retry the request. If the resource is being resynchronized, retry the operation later. |
| 609 | Invalid data received for <a character string>.
Meaning: The LNM OS/2 Agent discovery application expected a character string which contained valid hex digits. Action: Verify that data being returned in run command responses is valid. Adapter addresses, segment numbers and concentrator ids are expected to be valid hex digits. If they are not, restart the LNM OS/2 Agent. If the problem persists, contact IBM Service for more information. |
| 610 | Return code <value> for <run command key words> run command
Meaning: With the exception of messages 804, 805, 808, 809, 810 and 833, prefix the value with DFI for the corresponding LNM OS/2 Agent message number. The run command key words tell which run command returned the DFI value. For the set enumerated above:
Action: The impact of the message is determined by the run command which generated the response and the value returned. For example, 488 indicates no adapters match the defined view. This is an acceptable response for a request for an adapter list for an unlinked segment which is connected by an unlinked bridge. In general, though this message will mean there is a loss of data and the representation of the network from LNM for AIX will be at best incomplete and possibly inaccurate. The explanation for the DFI messages is documented by the LNM OS/2 Agent. The following list addresses those return code values which do not correspond to a DFI message from LNM OS/2 Agent.
|
| 611 | Duplicate adapter <adapter address> on segment <segment
number>.
Meaning: An adapter address has been found more than once on the same segment. The additional occurrences of the adapter will not display. Any adapter specific traps will be correlated and applied to the first occurrence. Action: If multiple Bridge link successful messages (OS/2 agent trap 458) come in at the same time for the same segment, ignore the warning. Otherwise, investigate the adapters on the segment to see if a duplicate exists. If so, change the locally administered address to make it unique. |
| 612 | Unexpected value <value> in switch statement in procedure
<procedure
name>
Meaning: The data does not conform to the expected set. Action: In general this indicates a programming error. If it does not reoccur it can be due to a failure in the transmission of data on the socket. If it reoccurs, contact IBM Service for more information. |
| 613 | Socket connection from <executable name> to <executable
name/trap session> failed
Meaning: The communications from the LNM OS/2 Agent discovery application to/from one of the other LNM for AIX components (cmld, lnmtopod, lnmlnmeint, lnmBaseTimer, lnmlnmemgr) or with NetView for AIX trap processing have been disrupted. There will be a loss of data. Action: If communications failed with the OVsnmp Trap Receiving Session, traps coming from the LNM OS/2 Agents to LNM for AIX have probably been lost. It may be necessary to manually resynchronize the agents or one or more segments, to display an accurate representation of the network. If communications failed with the OVsnmp Trap Sending Session, traps with the correlation data have probably been lost and will not reflect in the trapd log or, if applicable, the event cards. No action is required. If communication fails with the Control program (cmld), the LNM OS/2 Agent components (lnmlnmemon, lnmlnmeint, lnmBaseTimer, and lnmlnmemgr) will terminate. Check the nettl log to see why communications failed. Correct the error indicated by the interprocess communication messages if possible. Try to restart the components using the command cmlstart. If this is unsuccessful, stop LNM for AIX and then restart LNM for AIX. If communications fail with lnmtopod, the LNM OS/2 Agent discovery application components will terminate. Check the nettl log to see why communications failed. Correct the error indicated by the interprocess communication messages if possible. Try to restart the components using the command cmlstart. If this is unsuccessful, stop LNM for AIX and then restart LNM for AIX. If communications fail with lnmlnmeint, there will be a disruption in the management but an attempt is made to recover. If it is possible to restart the interface component, the LNM OS/2 Agent discovery application will check the status of each known agent. If an agent was in the middle of a discovery cycle, the discovery process will be restarted. If an agent was in an idle state, connection will be reestablished. If communications fails with lnmBaseTimer, an attempt is made to recover. Timed events are resubmitted but times are not recalculated. This will impact the accuracy of history collection times and scheduled resyncs. If communication fails with the lnmlnmemgr, an attempt is made to recover. If lnmlnmemgr is not running, attempting to access an OS/2 agent management window will restart it. |
| 615 | Duplicate resynchronize request for LNM OS/2 Agent <IP address>
segment <segment number>
Meaning: If a particular segment is being resynchronized and an additional request is received to resynchronize it, this message is written to the log and the request is discarded. Action: None. |
| 616 | Request for duplicate resource <IP address>
Meaning: A request to discover a known agent has been received. It is discarded. Action: None. |
| 619 | Invalid ring interval found in file = <IP address.conf>
Meaning: The ring utilization interval must be from 60 seconds to 86360 seconds (23 hours 59 minutes). Action: Use the Segment Parameters window to correct the error. |
| 620 | Invalid segment start/stop date found in file = <IP
address.conf>
Meaning: The start and stop date must be from 0 to 6 (Sunday through Saturday). Action: Use the Segment Parameters window to correct the date in error. |
| 621 | Invalid segment start/stop time found in file = <IP
address.conf>
Meaning: The start and stop time must be from 0 to 1439 minutes (0 hours and minutes to 23 hours and 59 minutes). Action: Use the Segment Parameters window to correct the time in error. |
| 622 | Invalid bridge start/stop date found in file = <IP
address.conf>
Meaning: The start and stop date must be from 0 to 6 (Sunday through Saturday). Action: Use the Bridge Parameters window to correct the date in error. |
| 623 | Invalid bridge start/stop time found in file = <IP
address.conf>
Meaning: The start and stop time must be from 0 to 1439 minutes (0 hours and minutes to 23 hours and 59 minutes). Action: Use the Bridge Parameters window to correct the time in error. |
| 628 | Could not set segment interval in file = <IP address.conf>
Meaning: The attempt to retrieve the required record from the agent configuration file failed. Action: Possible reasons for the failure are:
|
| 629 | Could not get segment interval in file = <IP address.conf>
Meaning: The attempt to retrieve the required record from the agent configuration file failed. Action: Possible reasons for the failure are:
|
| 630 | Could not set bridge interval in file = <IP address.conf>
Meaning: The attempt to retrieve the required record from the agent configuration file failed. Action: Possible reasons for the failure are:
|
| 631 | Could not get bridge interval in file = <IP address.conf>
Meaning: The attempt to retrieve the required record from the agent configuration file failed. Action: Possible reasons for the failure are:
|
| 632 | Could not get bridge graph lines in file = <IP address.conf>
Meaning: The attempt to retrieve the required record from the agent configuration file failed. This information is used by the LNM OS/2 Agent management application to populate Bridge Performance Window with the last known choices. Action: Possible reasons for the failure are:
|
| 633 | Cannot open history file = <history file name> with access
= a+ Error <value>: <error description>
Meaning: The file cannot be opened in append mode. This mode opens a file for writing at the end of the file, or creates a file for writing. Action: Correct the error so that future collection will be successful. There will be a loss of data. |
| 635 | lnmlnmemon exiting. Exit code <exit status>
Meaning: lnmlnmemon is terminating for one of the following reasons:
Action: This message can be used in conjunction with the response from cmlstatus to understand why lnmlnmemon is no longer running. See the man page for cmlstatus for an explanation of the exit codes. If this message is not written to the log, lnmlnmemon was terminated using SIGKILL or terminated abnormally. If lnmlnmemon terminated abnormally, a core dump will probably be found in the root directory. You can determine the executable that generated a core dump by entering the following command while you are in the directory with the core image od -c core 0x4850 | head Record the information from executing dbx with the where subcommand or the t subcommand. Contact IBM Service for more information. |
| 636 | Refresh of LNM OS/2 Agent <IP address> is in progress
Meaning: If a particular agent is being refreshed and an additional request is received to refresh it, this message is written to the log and the request is discarded. Action: None. |
| 637 | LNM OS/2 Agent <IP address> is initializing or resyncing.
Discovery of the agent topology will be retried in <n>
minutes.
Meaning: The LNM OS/2 Agent is busy gathering its view of the network. To allow this to complete as quickly as possible, the LNM OS/2 Agent discovery application will not request any more information for n minutes. The LNM OS/2 Agent discovery application will attempt to restart the discovery process for the agent, every n minutes until it is successful. Successful means that the LNM OS/2 Agent has completed establishing its view of the network. The length of delay is dependent on the size of the network the LNM OS/2 Agent is handling, the hardware the agent is running on and what is running on that hardware. Action: None. |
| 638 | Limits for loading the initial configuration for the LNM OS/2 agent
<IP
address> have been exceeded. There may be data loss.
Meaning: The load of local configuration information is limited to 250 bridge definitions and 260 adapter definitions. In addition there can be no more than 250 bridge definitions or 255 segments currently known to the LNM OS/2 Agent. If the limits are exceeded a partial load will be carried out. Action: Use the end user interface to complete the configuration process. |
| 639 | The resource <resource name> is not within the LNM OS/2 Agent
managed domain.
Meaning: LNM for AIX received a trap 751 (new CAU) from an LNM OS/2 Agent. The segment in the trap is not within the LNM OS/2 Agent domain. Therefore the segment and CAU will not be added to the graphical display. Action: If the intent is to manage the segment, add a CAU qualifier for the segment or link a bridge which handles the segment. Otherwise no action is required. |
| 641 | Cannot process response for LNM OS/2 Agent <IP address> adapter
<adapter
address>. Procedure = <procedure name> File =
<file
name>, Line = <line number>
Meaning: The initial configuration processing has received a run command response for which it does not have a matching request. Action: This is not expected to occur. It is unlikely that the configuration and discovery of the LNM OS/2 Agent will complete successfully. If this messages occurs, remove the LNM OS/2 Agent and retry the operation. If it does not reoccur it could be caused by corruption of the transmitted data. If it reoccurs, contact IBM Service for more information. |
| 642 | Bridge <bridge name> is a multiport bridge. Procedure
= <procedure name> File = <file name>, Line = <line
number>
Meaning: If an icon has been created for a bridge that the LNM OS/2 agent classifies as a multiport bridge when it responds to LAN BRG QUERY NAME=<bridge name> ATTR=RPT, the bridge is no longer manageable from the LNM OS/2 component of LNM for AIX. The icon is deleted from the LAN submap. Action: None. |
| 643 | Unexpected segment type <segment type> Procedure =
<procedure
name> File = <file name>, Line = <line number>
Meaning: There is an inconsistency in the expected data and the data received. Action: If the problem persists, collect trace files for the processes lnmlnmemon and lnmlnmeint. Contact IBM Service for more information. |
| 644 | Received AGENT_FOUND message from <process>, IP=<IP
address>.
Meaning: This message is written to the log if the agent is included in the set of agents managed by the LNM OS/2 component. Action: None. |
| 645 | Received AGENT_REMOVE message from <process>, IP=<IP
address>.
Meaning: This message is written to the log if the agent is removed from the set of agents managed by the LNM OS/2 component. Action: None. |
| 702 | Starting lnmlnmemgr.
Meaning: This message is written to the log when lnmlnmemgr is invoked. Action: None. |
| 703 | Stopping lnmlnmemgr.
Meaning: This message is written to the log when lnmlnmemgr terminates normally. Action: None. |
| 706 | No history data exists for segment <segment number>.
Meaning: There are no files in /usr/CML/reports/lnmlnmemon/<IP address> for the segment requested. The current file is seg<segment number>.history.01 and the file for the previous period is seg<segment number>.history.02. Action: If data was expected for the current period, verify that history collection is enabled for the segment and that the current period's interval spans the time during which the request was made. Check the log to ensure that ring utilization data is available for this segment. No file is created until there is data to put in it. There will not be a ...history.02 file until the collection window expires for the first time and a ...history.01 had been created. |
| 707 | No history data exists for bridge <bridge name>.
Meaning: There are no files in /usr/CML/reports/lnmlnmemon/<IP address> for the bridge requested. The current file is brg<bridge name>.history.01 and the file for the previous period is brg<bridge name>.history.02. Action: If data was expected for the current period, verify that history collection is enabled for the bridge and that the current period's interval spans the time during which the request was made. Check the bridge performance window to ensure the performance notification interval is greater than 0. Check the trapd.log to ensure that trap 801 is being received from the bridge. No file is created until there is data to put in it. There will not be a ...history.02 file until the collection window expires for the first time and a ...history.01 had been created. |
| 709 | A graph for segment <segment number> already exists.
Meaning: A graph window is currently open for this segment. Action: Close the open graph window for this segment and retry. |
| 710 | A graph for bridge <bridge name> already exists.
Meaning: A graph window is currently open for this bridge. Action: Close the open graph window for this bridge and retry. |
| 712 | Selecting OK would enable the Module.
Meaning: The selected action will generate a run command request for the LNM OS/2 Agent to have the module enabled. Action: Select OK or Cancel. |
| 713 | Selecting OK would disable the Module.
Meaning: The selected action will generate a run command request for the LNM OS/2 Agent to have the module disabled. Action: Select OK or Cancel. |
| 714 | Selecting OK would enable the lobe.
Meaning: The selected action will generate a run command request for the LNM OS/2 Agent to have the lobe enabled. Action: Select OK or Cancel. |
| 715 | Selecting OK would disable the lobe.
Meaning: The selected action will generate a run command request for the LNM OS/2 Agent to have the lobe disabled. Action: Select OK or Cancel. |
| 716 | <executable> terminated.
Meaning: The named executable has terminated. Action: If you have selected to stop LNM for AIX, this is only information. However, if you have not, this indicates that the executable in question has dropped the socket connection with lnmlnmemgr. Check the nettl log and execute cmlstatus for additional information on why the executable terminated. If lnmlnmeint terminates and lnmlnmemon does not, lnmlnmemon will attempt to restart lnmlnmeint. |
| 717 | Communication Error - Socket cannot be opened.
Meaning: Socket communications could not be established with lnmlnmemon or lnmlnmeint. Action: Check the nettl log to determine why the attempt to establish communications failed. |
| 719 | You are about to remove the adapter from the network.
Meaning: Once removed, the adapter will no longer be able to communicate with the network in any way. Manual intervention at the workstation will probably be required to restore the adapter's ability to communicate with the network. Note that the removal of an adapter may adversely effect the operation of a ring. Action: To proceed, select OK. To cancel the request, select Cancel. |
| 721 | Request could not be deleted from the list.
Meaning: An attempt to delete an entry from the list of outstanding requests failed. Action: None. |
| 725 | Receive system call failed.
Meaning: The read call on the socket failed. Action: Check the nettl log to determine why the call failed. |
| 726 | Syntax Error reported by the LNM OS/2 Agent.
Meaning: The run command contained a syntax error. Action: In general this indicates a programming error. Retry the operation. If it does not reoccur, it can be due to a failure in the transmission of data on the socket. If it reoccurs, contact IBM Service for more information. |
| 727 | Missing Station definition parameters. Adapter Address and
Adapter
Name are required to define a station.
Meaning: The adapter name and address are required for a station definition. Action: Enter the missing information and retry the operation. |
| 728 | Missing Bridge definition parameters. Bridge Name, Adapter1
Address and Adapter2 Address are required to define a bridge.
Meaning: The bridge name and two adapter addresses are required for a bridge definition. Action: Enter the missing information and retry the operation. |
| 729 | Missing Concentrator definition parameter. Concentrator ID is
required to define a Concentrator.
Meaning: The concentrator name is required for a Concentrator definition. Action: Enter the missing information and retry the operation. |
| 730 | Missing Concentrator Qualifier definition parameter. Segment
Number is required to define a Concentrator Qualifier.
Meaning: A segment number is required for a Concentrator Qualifier definition. Action: Enter the missing information and retry the operation. |
| 731 | You are about to delete the definition of the bridge. Select
OK to delete the definition, Cancel to Abort.
Meaning: The action you have selected will request the LNM OS/2 Agent to delete the bridge definition from its database. Action: Select Enter or Cancel. |
| 732 | You are about to delete the definition of the Concentrator.
Select OK to delete the definition, Cancel to Abort.
Meaning: The action you have selected will request the LNM OS/2 Agent to delete the concentrator definition from its database. Action: Select Enter or Cancel. |
| 733 | Missing Mapped Address parameters. Token Ring and Ethernet
Addresses
are required to add a mapped entry.
Meaning: The Token Ring and Ethernet adapter addresses are required to add a mapped entry. Action: Enter the missing information and retry the operation. |
| 734 | You are about to restart the Concentrator. Select OK to
restart,
Cancel to Abort
Meaning: The action you have selected will request the LNM OS/2 Agent to restart the concentrator. Action: Select OK or Cancel. |
| 735 | Communication Error - NO Data.
Meaning: An error occurred when lnmlnmemgr tried to send a request to initially populate a window to either lnmlnmeint or lnmlnmemgr. Action: Verify that lnmlnmeint and lnmlnmemon are running. Retry the operation. |
| 736 | Communication Error - OLD Data.
Meaning: An error occurred when lnmlnmemgr tried to send a request to refresh a window to either lnmlnmeint or lnmlnmemgr. Action: Verify that lnmlnmeint and lnmlnmemon are running. Retry the operation. |
| 737 | Error while waiting for responses.
Meaning: One or more of the fields on the window cannot be populated for the following reasons:
Action: Check the nettl log to determine the cause of the problem.
|
| 738 | Missing Remote Program Update definition parameter. File name
is required to update the Remote Program.
Meaning: The file name is required for Remote program update. Action: Enter the missing information and retry the operation. |
| 739 | The NLS catalog file <filename> was not found.
Meaning: The named catalog file was not found. Action: Verify there were no errors during installation. Verify the environment variable LANG is set to a language installed on your workstation. Verify that the correct locale is installed on your workstation using the locale and locale -a commands. locale will display whether the LC_MESSAGES field is the same as the LANG field. If not, try typing locale -a to display all the locales installed on your workstation. If the proper one is not loaded for your country you need to have it installed. Verify that the following conditions are true:
If everything is correctly set, contact IBM Service for more information. |
| 740 | Fatal Error. RC=<value>
Meaning: The LNM OS/2 Agent management application cannot run. In general an error message will be found in the log with the same number as the RC value. This is not true if an error occurred when trying to establish the socket connection with lnmlnmemon or lnmlnmeint. However there should be messages in the nettl log that indicate a socket call failure. The value returned indicates one of the following
Action: Check the nettl log for message 703 which indicates that lnmlnmemgr has terminated. Look back through the log for additional messages that indicate why lnmlnmemgr cannot run. |
| 741 | Resync failed on segment <segment number>.
Meaning: This error is displayed if the selected segment is not a Token Ring segment or the DFI message returned by the LNM OS/2 Agent for the request is not 999. Action: If the selected segment is a Token Ring segment, check the nettl log for why the resynchronize request failed. |
| 742 | Invalid range of the attribute Please try again.
Meaning: The value entered is not valid. Action: Enter a value within the attribute's range. |
| 744 | Unable to get data for this attribute.
Meaning: The LNM OS/2 Agent discovery application was unable to retrieve the data necessary for the LNM for AIX management application to populate the window. Either the LNM OS/2 Agent has not been discovered during this session or the agent configuration file is corrupted. Action: If the connection with the LNM OS/2 Agent has not been established, discover the agent using the SMIT windows or the command line script cml_agent_found. If the agent configuration file <IP address.conf> in the /usr/CML/conf/lnmlnmemon directory is corrupted, delete the file and recreate it using SMIT. If you delete the file and were collecting history on any segments or bridges, you will need to re-enable collection on those segments and bridges and reset the collection window. |
| 745 | Could not connect to <executable>.
Meaning: The LNM for AIX management application is unable to establish a connection with the named executable. Action: Use the nettl log and cmlstatus to determine why the executable is not running. |
| 747 | Could not connect to <executable> and <executable>.
Meaning: The LNM for AIX management application is unable to establish a connection with the named executables. Action: Use the nettl log and cmlstatus to determine why the executables are not running. |
| 748 | Interval cannot be less than 1 minute.
Meaning: The minimum value for the history collection interval for ring utilization is 1 minute. Action: Choose a value of 1 or more. If you do not want history collected for the segment, disable collection for the segment. |
| 749 | Unable to communicate with adapter. Last known data is
displayed.
Meaning: You specified an adapter that is not active on the specified LAN segment at the time of the request. The information shown is from the data in the LNM OS/2 Agent database. Action: None. |
| 750 | Segment test for segment <segment number> completed
successfully.
Meaning: The LNM OS/2 Agent successfully tested the named segment's data-transfer capability. Action: None. |
| 751 | Resync completed successfully on segment <segment number>.
Meaning: The LNM OS/2 Agent was able to successfully complete the request to resynchronize the segment. The LNM for AIX view is being refreshed. Action: None. |
| 752 | Resync started on segment <segment number>.
Meaning: A message has been sent to the LNM OS/2 Agent discovery application to initiate a resynchronize for the named segment. Action: None. |
| 753 | You are about to restart the LNM OS/2 Agent <IP address>.
Select OK to restart, Cancel to Abort
Meaning: You have selected an action to request that the LNM OS/2 Agent be restarted. This action will fail if the agent is not currently within the LNM for AIX managed domain or LNM for AIX cannot communicate with LNM OS/2 Agent. If this action succeeds management of the LNM OS/2 Agent will be temporarily disrupted. Action: Select OK or Cancel. |
| 754 | Submitted request for LNM OS/2 Agent <IP address> to be
restarted.
Meaning: A message has been sent to the interface component to inform the LNM OS/2 Agent to restart. The agent must be currently being managed by LNM for AIX for this request to be processed. Action: None. |
| 755 | Timeout occurred while waiting for a response.
Meaning: A run command has timed out. Action: No response was received from the LNM OS/2 Agent. A run command response is expected to be received from the LNM OS/2 Agent within a designated time period. This time period is the sum of the LNM for AIX response time (transmission time, network congestion, etc) and the LNM OS/2 Agent response time multiplied by the number of requests that are currently on the LNM OS/2 Agent queue from LNM for AIX. The response time components can be set from SMIT or from the LNM OS/2 Agent Configuration windows. Initially the response time out values may need to be adjusted to reflect the realities of the network. Once a successful set of values have been selected, the occurrence of a time-out may indicate increased network traffic or that the agent is now located more hops away from LNM for AIX and the LNM for AIX response time needs to increase or it may indicate that the agent is unable to communicate with LNM for AIX but the socket connections have not gone down. DCAF or TELNET can be used to determine the state of the agent workstation if it is located remotely. |
| 756 | You are about to delete the definition of the selected bridge(s).
Select OK to delete the definition(s), Cancel to Abort
Meaning: Delete requests will be transmitted to the LNM OS/2 Agent. A message box will be displayed for each request that fails. You will need to refresh the list to determine the request that failed. Action: To proceed, select OK. To cancel the request, select Cancel. |
| 757 | You are about to delete the definition of the selected
Concentrators(s).
Select OK to delete the definition(s), Cancel to Abort
Meaning: Delete requests will be transmitted to the LNM OS/2 Agent. A message box will be displayed for each request that fails. You will need to refresh the list to determine the request that failed. Action: To proceed, select OK. To cancel the request, select Cancel. |
| 758 | You are about to delete the definition of the selected adapter(s).
Select OK to delete the definition(s), Cancel to Abort
Meaning: Delete requests will be transmitted to the LNM OS/2 Agent. A message box will be displayed for each request that fails. You will need to refresh the list to determine the request that failed. Action: To proceed, select OK. To cancel the request, select Cancel. |
| 759 | You are about to remove the selected adapter(s) from the network.
Meaning: Once removed, the adapter(s) will no longer be able to communicate with the network in any way. Manual intervention at the workstation will probably be required to restore an adapter's ability to communicate with the network. Note that the removal of an adapter may adversely effect the operation of a ring. Remove requests will be transmitted to the LNM OS/2 Agent. A message box will be displayed for each request that fails. You will need to refresh the list to determine the request that failed. Action: To proceed, select OK. To cancel the request, select Cancel. |
| 760 | You have modified the default reporting link. To ensure bridges
using the default reporting link are reset, restart the LNM OS/2 Agent.
Meaning: The default reporting link has changed. Action: If the setting for the Automatic bridge relink parameter has been set to Active on the LNM OS/2 agent, the agent will unlink all bridges defined to use the default reporting link and then relink them according to the new reporting link value. To verify the setting for Automatic bridge relink, telnet into the LNM OS/2 agent machine and enter the following command: LAN SYSP QUERY ATTR=BRG If Automatic bridge relink is set to Inactive, it is recommended that you restart the LNM OS/2 agent. If you prefer, you can manually unlink and relink each of the bridges that is defined to use the default reporting link. On the LNM OS/2 agent, the default value for Automatic bridge relink is Inactive. |
| 801 | Trying to remove a connection that is not connected: <IP
address>
Meaning: The interface component has received a request to close the connection between the interface component and the designated LNM OS/2 Agent. The interface component has no record of the designated LNM OS/2 Agent. Action: In general this is not expected to occur. The exception case is when the socket connections have been disrupted between LNM for AIX and the LNM OS/2 Agent for an agent discovered during this session. Executing an cml_agent_remove or any action that causes lnmlnmemon to shutdown before an attempt is made by the LNM OS/2 Agent discovery application to have the connection reinstated could lead to this error. In all other cases, it would be a programming error. If the problem occurs in any scenario other than that described above, contact IBM Service for more information. |
| 802 | Trying to add a connection that is already connected: <IP
address>
Meaning: The interface component has received a request to establish a connection with an LNM OS/2 Agent with which it already has a connection. Action: None. |
| 803 | Cannot connect to LNM OS/2 Agent with Internet address: <IP
address>
Meaning: The interface component cannot establish a socket connection with the LNM OS/2 Agent. Action: Verify the following:
|
| 804 | No Internet address matches the destination of the run command:
<IP
address>
Meaning: The interface component has received a request to transmit a run command to an unknown agent. This occurs if a request is sent from the LNM OS/2 Agent management application before an attempt to discover the agent by the LNM OS/2 Agent discovery application is made during this session or the agent is temporarily unavailable due to a RESTART request or failure of the socket from the interface component to the LNM OS/2 Agent. Action: Review the nettl log to determine if a connection to the agent has not been established (message 803). If no cml_agent_found has been executed for the agent during this session, issue one. If a RESTART was requested, retry the operation later. |
| 805 | The socket connection is broken from lnmlnmeint to one of its
clients.
Bytes received = <number of bytes read>
Meaning: This message will be written when a socket connection is closed or fails between lnmlnmeint and lnmlnmemgr or lnmlnmemon. If bytes received if less than 0 a socket has closed, otherwise an error has occurred in the read system call. Action: If an LNM OS/2 Agent has just been removed or a shutdown has been issued, it will be normal to see this message and bytes received should be zero. However, if communications do not seem to be functioning properly and this message is in the log, look for earlier indications in the log for why the interprocess communications are failing. |
| 806 | Connection failure for LNM OS/2 Agent at: <IP address>
Meaning: Either a send or receive on the Internet socket returned a socket error or indicated that the socket is closed. Action: If the LNM OS/2 Agent was exited or the workstation was shutdown deliberately, no action is required. Otherwise, use the nettl log and trapd.log for an indication of why the connection to the LNM OS/2 Agent was dropped. DCAF or TELNET can be used to determine the state of the agent workstation if it is located remotely. |
| 807 | Unidentified data received and ignored. Agent <IP
address>
Command Type <command mapping> Data = < dump of part of the
buffer > File = <source file name>, Line = <line number>
Meaning: Data returned to the interface component as a run command response did not match the expected response format. The first part of the response is written to the log. Only commands which return data in the response are mapped to a command type. The commands that return data in the response and are used by the LNM OS/2 Agent discovery and management applications are described in the following list:
Action: It is possible for this situation to occur if the data on the socket is corrupted. Verify the run command is returning a valid response by executing it in the OS/2 window. If the response is valid, retry the operation. If the problem persists, contact IBM Service for more information. |
| 808 | Received more than maximum supported adapter entries. The
excess
entries are discarded. Agent <IP address> File =
<source
file name>, Line = <line number>
Meaning: The LNM for AIX application supports a maximum of 500 adapters in the run command responses for any LAN ADP LIST, LAN BRG QUERY ATTR=MAPPED or LAN BRG QUERY ATTR=STATIC request. Action: Remove unnecessary adapter definitions. |
| 809 | Received more than maximum supported bridge entries. The
excess
entries are discarded. Agent <IP address> File =
<source
file name>, Line = <line number>
Meaning: The LNM for AIX application supports a maximum of 500 bridges in any LAN BRG LIST run command response. Action: Remove unnecessary bridge definitions. |
| 810 | Received more than maximum supported Concentrator entries.
The
excess entries are discarded. Agent <IP address> File =
<source
file name>, Line = <line number>
Meaning: The LNM for AIX application supports a maximum of 1000 concentrators in the LAN CAU LIST run command response. Action: Remove unnecessary concentrator definitions. |
| 811 | The LNM OS/2 Agent <IP address> cannot execute the LAN
command.
Error code = <value>, File = <source file name>, Line
= <line number>
Meaning: The LNM OS/2 Agent program is unable to process the run command. Action: The action depends on the error code:
|
| 812 | The LNM OS/2 Agent <IP address> cannot set the trap filter.
File = <source file name>, Line = <line number>
Meaning: The request to enable or disable traps failed. LNM for AIX will continue to process run commands but the status of the topology display will only be as current as the last refresh of the agent view on LNM for AIX. Action: The action depends on the error code:
|
| 813 | Unknown command received at the LNM OS/2 agent <IP address>.
File = <source file name>, Line = <line number>
Meaning: A run command request has been received by the interface component that is not within the set of commands it is set up to handle. Action: It is possible for this situation to occur if the data on the socket is corrupted. Retry the operation. If the condition persists, contact IBM Service for more information. |
| 814 | A timeout occurred on an LNM OS/2 Agent <IP address> correlator
= <correlator>.
Meaning: A run command has timed out. Action: No response was received from the LNM OS/2 Agent. A run command response is expected to be received from the LNM OS/2 Agent within a designated time period. This time period is the sum of the LNM for AIX response time (transmission time, network congestion, etc) and the LNM OS/2 Agent response time multiplied by the number of requests that are currently on the LNM OS/2 Agent queue from LNM for AIX. The response time components can be set from SMIT or from the LNM OS/2 Agent Configuration windows. Initially the response time out values may need to be adjusted to reflect the realities of the network. Once a successful set of values have been selected, the occurrence of a time-out may indicate increased network traffic or that the agent is now located more hops away from LNM for AIX and the LNM for AIX response time needs to increase or it may indicate that the agent is unable to communicate with LNM for AIX but the socket connections have not gone down. DCAF or TELNET can be used to determine the state of the agent workstation if it is located remotely. |
| 818 | Unexpected value <value> in switch statement in procedure
<procedure
name> File = <source file name>, Line = <line number>
Meaning: The data does not conform to the expected set. Action: In general this indicates a programming error. If it does not reoccur it can be due to a failure in the transmission of data on the socket. If it reoccurs, contact IBM Service for more information. |
| 820 | Socket connection from lnmlnmeint to lnmBaseTimer failed
Meaning: A communications error has been detected, an attempt is made to recover. Timed events are resubmitted but times are not recalculated. Action: Check the nettl log to determine why communications failed. |
| 821 | Received more than maximum supported concentrator qualifier
entries.
The excess entries are discarded. Agent <IP address>
File = <source file name>, Line = <line number> Meaning: The LNM for AIX application supports a maximum of 256 concentrator qualifiers in the LAN CAUQUAL LIST run command response. Action: Remove unnecessary concentrator qualifier definitions. |
| 901 | SNMP error -- OVsnmpErrno: <error number>, nvSnmpErrno:
<NetView
error number> , nvSnmpSubsys: <NetView snmp subsystem>,
File:<file
name>, Line:<line number>
Meaning: The trap processor failed in an attempt to open a session with NetView for AIX to send a trap. Action: Look at the man page for OVsnmpOpen. The error codes should help you determine the correct action to take. If they do not, then shut down and restart LAN Network Manager for AIX and NetView for AIX. If the problem persists, contact IBM Service for more information. |
| 902 | Unable to close SNMP session -- OVsnmpErrno: <error number>
File: <file name>, Line: <line number>
Meaning: The trap processor has failed in an attempt to close a trap session with NetView for AIX. Action: Look at the man page for OVsnmpClose. The error code should help you determine the correct action if any to take to take. If traps are continuing to flow from AIX NetView/6000 to LNM for AIX and back for all monitored agents, no action additional action is necessary. If the trap flow does not recover, then shut down and restart LAN Network Manager for AIX and NetView for AIX. If trap processing cannot be recovered, contact IBM Service for more information. |
| 903 | Unable to get filter from NetView for AIX, return code is <return
code>.
File: <file name>, Line: <line number>
Meaning: The trap processor has failed in an attempt to retrieve a trap filter file. Action: Look at the man page for nvFilterGet. The error code should help you determine the correct action to take. If it does not, then shut down and restart LAN Network Manager for AIX and NetView for AIX. Both applications must be started with root privileges. If the problem persists, contact IBM Service for more information. |
| 905 | Attempt to delete unknown agent <agent name>. File:
<file
name>, Line: <line number>
Meaning: An application is attempting to delete an agent that is unknown to the trap processor. Action: None. If the problem persists, contact IBM Service for more information. |
| 906 | Unable to create trap -- OVsnmpErrno: <error number>.
File: <file name>, Line: <line number>
Meaning: The trap processor failed in an attempt to build a trap to send to NetView for AIX. Action: Look at the man page for OVsnmpCreatePdu. The error code should help you determine the correct action to take. If it does not, then shut down and restart LAN Network Manager for AIX and NetView for AIX. If the problem persists, contact IBM Service for more information. |
| 907 | Unable to send trap -- OVsnmpErrno: <error number>.
File: <file
name>, Line: <line number>
Meaning: The trap processor failed in an attempt to send a trap to NetView for AIX. Action: Look at the man page for OVsnmpSend. The error code should help you determine the correct action to take. If it does not, then shut down and restart LAN Network Manager for AIX and NetView for AIX. If the problem persists, contact IBM Service for more information. |
| 910 | Received invalid trap. File: <file name>, Line:
<line
number>
Meaning: Validation failed on a trap sent from the agent to LAN Network Manager for AIX. Action: None; the trap may have just be corrupted during transmission. If the problem persists, contact IBM Service for more information. |
| 951 | LNM databases are already empty.
Meaning: No LNM objects were found in the database. Action: None. |
| 952 | LNM databases will be cleared.
Proceed Y/N ? Meaning: You have requested that all LNM objects be removed from the database. Action: Type Y if you wish to continue; otherwise, type N to cancel the operation. |
| 955 | Unable to send message number <message_number> to ATM
topology.
Return code was <return_code>.
Meaning: A communication failure occurred between a ahmtopod and lnmtopod. Action: Ensure ovstatus |
| 956 | Started up ATM topology interface.
Meaning: This message is written to the log when ahmtopod sends a start message to lnmtopod. Action: None. |
| 957 | Shutting down interface with ATM topology.
Meaning: This message is written to the log when lnmtopod receives a shutdown message and there is a start message from ahmtopod during the same session. Action: None. |
| 960 | nvot_server connection was not established.
Meaning: Topology Services was unable to connect to the nvot_server daemon. Action: Use ovstatus to determine why the nvot_server daemon is not running. Use ovstart nvot_server to start the daemon. Restart LNM for AIX using ovstart cmld. |
| 961 | nvot_server connection already established.
Meaning: A connection with the nvot_server daemon was established already when another attempt to do so was made. Action: None. |
| 1000-1999 | Message received from the OS/2 agent program.
Meaning: Messages with numbers between 1000 and 1999 are sent to LAN Network Manager from the OS/2 agent program. Action: Refer to the documentation that is provided with the OS/2 agent for an explanation of the message and suggested actions to take to resolve the problem. LAN Network Manager appends a 1 to the front of the message number that it receives from the OS/2 agent. Before consulting the agent documentation, identify the appropriate message number for the OS/2 agent by removing the 1 from the number. For example, message number 1300 on LAN Network Manager corresponds to message number 300 on the OS/2 agent. |
| 2001 | Starting lnmbrmgr.
Meaning: The bridge management application has started. Action: None. |
| 2002 | Stopping lnmbrmgr.
Meaning: The bridge management application has terminated due to NetView for AIX terminating or because of an unexpected error. Action: None. |
| 2003 | The NLS catalog file <filename> was not found.
Meaning: The bridge management application was unable to open the specified catalog file. Default text will be displayed in English. Action: Ensure the environment variables LANG and NLSPATH are properly set for your AIX workstation. Also, be sure the correct locale is installed on your AIX workstation. |
| 2004 | lnmbrmon terminated.
Meaning: The bridge discovery application has terminated while the bridge management application had a socket connection with it. Action: If you did not intend to stop the bridge discovery application, you can restart it with cmlstart. |
| 2005 | lnmbrmon socket has failed.
Meaning: The bridge management application was unable to communicate with the bridge discovery application because of a severe error. Action: The bridge management application will shutdown immediately. Stop and restart LAN Network Manager. |
| 2006 | lnmbrmon is not running.
Meaning: The bridge management application was unable to communicate with the bridge discovery application because the bridge discovery application is not running. Action: Stop and restart LAN Network Manager. |
| 2007 | Unable to open socket to lnmbrmon.
Meaning: The bridge management application was unable to communicate with the bridge discovery application because of a severe error. Action: Stop and restart LAN Network Manager and NetView for AIX. |
| 2008 | SNMP timeout on request.
Meaning: An SNMP request timed out because the IP address is not valid or the community name is not valid. Action: Verify that the IP address is correct. Verify that the IP address exists on the network (ping the address). Verify that the community name is correct using the NetView for AIX SNMP Configuration option. Increase the timeout interval. If that fails, contact IBM Service for more information. |
| 2010 | SNMP noSuchName error. For a set, the value is read-only or the
community name is not valid.
Meaning: The requested SNMP OID does not exist on the SNMP agent. If you are attempting to set a value, the value may be read-only or you may be using a community name that is not valid. Action: If this SNMP OID is not supported by the SNMP agent, no value can be retrieved and displayed to the user. If a value is displayed and you are trying to change it, ensure you are using the proper community name. Check the SNMP Configuration from NetView for AIX and the SNMP community name on the agent that allows read/write authority. |
| 2011 | SNMP badValue error.
Meaning: An attempt to SET an SNMP OID has failed because the value is outside the allowable values. Action: Check the value you are trying to set and ensure it is valid. Retry the operation. |
| 2012 | SNMP readOnly error.
Meaning: The SNMP OID you are trying to set is read only. Action: Since this SNMP OID is read only on the SNMP agent you will not be allowed to set it. |
| 2015 | Memory allocation failed.
Meaning: The bridge management application was unable to allocate memory. Action: In the short term, shut down some other applications, then restart LAN Network Manager. In the long term, obtain more memory. |
| 2018 | Cannot establish an SNMP session.
Meaning: The bridge management application was unable to open an SNMP session using the NetView for AIX API services. Action: Close several windows and retry the operation. If the problem persists, stop and restart NetView for AIX and LAN Network Manager and retry the operation. |
| 2022 | This parameter is below the minimum value.
Meaning: The parameter you are attempting to set is below the minimum value. Action: Increase the value so that it is equal to or greater than the minimum value and retry the operation. |
| 2023 | This parameter is above the maximum value.
Meaning: The parameter you are attempting to set is above the maximum value. Action: Decrease the value so that it is equal to or less than the maximum value and retry the operation. |
| 2024 | Resync started for subnet <name>.
Meaning: The user has requested that a resynchronize be done for the specified subnet. Action: None. The user will be notified when the resynchronize completes. |
| 2025 | Polling started for agent <name>.
Meaning: The user has requested that a poll be done for the specified agent. Action: None. The user will be notified when the poll completes. |
| 2026 | Resync completed for subnet <name>.
Meaning: A user requested resynchronize has completed. Action: None. |
| 2027 | Polling completed for agent <name>.
Meaning: A user requested poll has completed. Action: None. |
| 2028 | Resync in progress for subnet <name>.
Meaning: The user requested to resynchronize the subnet but a resync is already in progress. Action: Wait for the resynchronize to complete before requesting another. |
| 2029 | Polling in progress for agent <name>.
Meaning: The user requested to poll the agent but a poll is already in progress. Action: Wait for the poll to complete before requesting another. |
| 2030 | Unable to read the configuration file.
Meaning: The bridge management application requested information from the bridge discovery application but the bridge discovery application was unable to read the information from the configuration file. Action: Use SMIT to verify the bridge SNMP application bridge parameters are correct. |
| 2031 | Unable to write to the configuration file.
Meaning: The bridge management application requested for the bridge discovery application to save information but the bridge discovery application was unable to write the information to the configuration file. Action: Use SMIT to verify the bridge SNMP application bridge parameters are correct. Try the same operation from the SMIT window. Also, verify that the user has write authority for the configuration file. |
| 2032 | No SNMP data was collected.
Meaning: This attribute is a combination of SNMP values. If any one of the SNMP values could not be collected, this message is used. Action: Verify that the SNMP OIDs used in this calculation are valid for the SNMP agent by selecting the Details push button. |
| 2033 | Starting the user definable device configuration program
<filename>.
Please read the documentation for more information about setting up this
option.
Meaning: The Device Configuration pushbutton on the Bridge Configuration window was selected and the specified script file has been executed. If you want to use other external configuration programs you can use this feature to invoke the programs from the bridge management application. Action: For more information on setting up this option, please refer to Using LAN Network Manager for AIX. |
| 2034 | Unable to run the device configuration program <filename>.
Meaning: The specified program was unable to be executed. Either you do not have execute authority or the program does not exist. Action: Verify that the program exists and you have the proper permissions to execute it. |
| 2101 | Cannot open SNMP session for agent. IP Address = <IP
address>
errno = <error number> File = <filename>, Line =
<line
number>
Meaning: The OVsnmpXOpen failed for the SNMP agent listed in the IP Address field. Action: Use the NetView/6000 reference manual and follow the instructions for the error number. |
| 2102 | SNMP get error for agent. IP Address = <IP address>
File = <filename>, Line = <line number>
Meaning: Error allocating the correlator for the SNMP get request. Action: Try stopping and restarting LNM for AIX. Contact IBM Service for more information. |
| 2103 | SNMP get response error for agent. IP Address = <IP
address>
File = <filename>, Line = <line number>
Meaning: A get request for the SNMP agent with the IP Address failed. Action: Verify that the SNMP agent is up by using the MIB browser and issuing get requests on the IP Address specified in the message. If the agent is working, stop and restart LNM for AIX. If that does not solve the problem, contact IBM Service for more information. |
| 2104 | Error: snmp unknown response IP Address = <IP address>
File = <filename>, Line = <line number>
Meaning: The SNMP bridge application received a NULL PDU from the agent. The bridge will be placed in the undiscovered subnet. Action: If the bridge is responding properly, it should be rediscovered the next time a poll request is issued. |
| 2105 | Error: Request ID failed in <function> IP Address
= <IP address> File = <filename>, Line = <line number>
Meaning: Error allocating the correlator for the SNMP get request. Action: Try stopping and restarting LNM for AIX. If the error persists, contact IBM Service for more information. |
| 2107 | Request for unknown resource <resource name> File =
<filename>,
Line = <line number>
Meaning: A delete agent was received, but the agent is not currently being managed by the bridge application. Action: The request is ignored. |
| 2108 | Unexpected value in switch statement Procedure <name>.
Switch value = <value> File = <filename>, Line = <line
number>
Meaning: This is a catch all message that dumps any unexpected values. The switch value will indicate the value that caused the error. The file can be used to determine the kind of problem that occurred. Action:
|
| 2109 | Socket connection from <executable> to <executable> failed
in <function>. Return Code= <rc>, File =
<filename>,
Line = <line number>
Meaning: This is a catch all message for socket errors. The connection that failed is identified by the component that is connected to lnnbrmon. The following is the action taken depending on the failing component. Action:
|
| 2111 | Request for duplicate resource <resource name>. File
= <filename>, Line = <line number>
Meaning: A duplicate agent found message has been detected. The duplicate request will be ignored. Action: None. |
| 2112 | Wrong response in <function>. type = <SNMP
response>,
IP Address = <IP address> File = <filename>, Line = <line
number>
Meaning: The bridge application issued a get or get-next request and it received an invalid SNMP response. The bridge will be placed in the undiscovered subnet. Action: This should not happen. Verify that the agent in the IP Address field is functioning properly. |
| 2113 | SNMP error in <function>. errorStatus = <number>,
IP Address = <IP address>, errorIndex = <number> File
= <filename>, Line = <line number>
Meaning: The bridge application received an SNMP error back from a get or get-next request. This is most likely an agent error. Action: Verify that the agent identified by IP the address works with the MIB browser. Verify that all MIB II(RFC 1213) and bridge(RFC 1286) attributes can be retrieved by the MIB browser. If you see this message in SnmpBrPort::processingPortIfIndex, check that there is an ifIndex in MIB II that corresponds to the RFC 1286 basePortIfIndex. This is a common problem with OS/2 bridges that use TCP/IP. The following example shows two base ports that map back to MIB II inIndex 1 and 2. In this example the MIB II ifIndex is missing for ifIndex 2, so the bridge cannot be discovered. MIB II ifType problems (OS/2 agents) ..ifTable.ifEntry.ifType.1 iso8802-tokenring RFC 1286 ..dot1dBasePortEntry.dot1dBasePortIfIndex.1 1 ..dot1dBasePortEntry.dot1dBasePortIfIndex.2 2 |
| 2114 | Wrong OID returned in <function>. errorStatus =
<number>,
IP Address = <IP address>, errorIndex = <number>,
OID = <object ID>, File = <filename>, Line = <line number>
Meaning: The bridge application received an SNMP error back from a get or get-next request. This is most likely an agent error. Action: Verify that the agent identify by the IP address works with MIB browser. Verify that all MIB II(RFC 1213) and bridge(RFC 1286) attributes can be retrieved by the MIB browser. |
| 2115 | No Matching Base port for <port type> Port in
<function>.
IP Address = <IP address>, OID = <object ID>, value
= <object value>, File = <filename>, Line = <line number>
Meaning: The bridge application maps the RFC 1286 SR, TP, and STP tables to the RFC 1286 BasePort table. Multiple algorithms are used to try to perform this mapping. In this case, the bridge application cannot map RFC 1286 ports for this bridge. Action: Dump the dot1dBridge attributes using the MIB browser verify that the number of SR, TP, STP, and base ports do not match. SR and TP ports are ignored if they do not match a base port. In this case below, dot1dSRPort.3 does not match and the bridge application will not report the port as an SR port. RFC 1286 ..dot1dBasePortEntry.dot1dBasePortIfIndex.1 1 ..dot1dBasePortEntry.dot1dBasePortIfIndex.2 2 ..dotd1dSrPortEntry.dot1dSRPort.1 : 1 ..dotd1dSrPortEntry.dot1dSRPort.2 : 2 ..dotd1dSrPortEntry.dot1dSRPort.3 : 3 If STP ports cannot be mapped to the base ports, the discovery for that bridge is terminated and the bridge is placed in the undiscovered subnet. RFC 1286 ..dot1dBasePortEntry.dot1dBasePortIfIndex.1 1 ..dot1dBasePortEntry.dot1dBasePortIfIndex.3 3 ..dotdStpPortEntry.dot1dStpPort.1 : 1 ..dotdStpPortEntry.dot1dStpPort.2 : 2 ..dotdStpPortEntry.dot1dStpPort.3 : 3 |
| 2116 | Unknown Port Type in <Procedure> IP Address = <IP
address>, MAC Address = <address>, IfIndex = <number>
File = <filename>, Line = <line number>
Meaning: The bridge application discovered a base port with the corresponding ifIndex that did not have a matching entry in the SR port table or the TP port table. Action: The bridge application will continue processing. This is a possible bridge configuration error, or a non-standard bridge. |
| 2117 | Wrong Interface Type in <function>. original interface
type = <number> new interface type = <number> segment
number = <number> desigBridge = <bridge>, desigPort =
<port>
File = <filename>, Line = <line number>
Meaning: The bridge application discovered the same segment with a different ifType. Action: Verify the bridge configuration. |
| 2119 | Trap from invalid agent with OID = <object ID> received
in <function>. File = <filename>, Line = <line
number>
Meaning: The bridge application received a trap from an agent that the bridge application does not support. The trap will be ignored. The IP Address identifies the bridge that is sending the traps. Action: Verify that the bridge filter files are correct. |
| 2120 | Cannot get text from the message catalog in <function>.
Default text = <text> Text ID = <number> File =
<filename>,
Line = <line number>
Meaning: The NLS catalog could not be open. This may be an installation problem. The bridge application will continue with default text in English. Action: Ensure the environment variables LANG and NLSPATH are properly set for your AIX workstation. Also, be sure the correct locale is installed on your AIX workstation. |
| 2121 | Error accessing the Bridge config file in = <function>.
Return code = <number> fileName = <filename>, record =
<record>
File = <filename>, Line = <line number>
Meaning: The bridge parameters window attempted to update the bridge configuration file /usr/CML/conf/lnmbrmon/lnmbrmon.default.conf The update failed. Action: Verify that the access permissions and owner are correct. |
| 2122 | Unexpected Trap in <function>. Generic number =
<number>,
specific Number = <number>, IP Address = <IP address>
File = <filename>, Line = <line number>
Meaning: The bridge application received a generic trap (RFC 1157). Action: This is a warning message so that traps about the community name are logged. |
| 2123 | Unexpected Bridge Configuration in <function>. IP
Address
= <IP address> File = <filename>, Line = <line number>
Meaning: The number of unique ifIndices found for this bridge was 0. Action: Verify the bridge configuration for the specified IP address. |
| 2124 | SNMP Time out <function>. type = <number> IP
Address
= <IP address> File = <filename>, Line = <line number>
Meaning: An SNMP timeout has occurred while attempting to discover or poll the bridge. The bridge will be placed in the undiscovered subnet. Action: Verify that the agent is up and that you can retrieve attributes using the MIB browser. If so, attempt to poll the bridge. If you still receive timeout messages, change the SNMP timeout parameters in NetView/6000. |
| 2125 | Socket connection from <executable> to <executable> failed
in <function>. errno = <number> File =
<filename>,
Line = <line number>
Meaning: The bridge application will recreate the socket and wait for the bridge window application to restart. Action:
|
| 2126 | Error communicating with the <executable> application in
<function>.
Correlator = <number> Resource = <name> File
= <filename>, Line = <line number>
Meaning: The bridge application has encountered an error while attempting to communicate with the management application. Action: This is a normal message if the management application terminates. The bridge application will continue processing. |
| 2128 | Subnet could not be found for agent. IP Address = <IP
address>
Not found in <function> File = <filename>, Line =
<line
number>
Meaning: The bridge application is receiving traps from an agent that it has not properly discovered. Action: Poll the bridge and then resynchronize the subnet. If that fails to solve the problem, stop and restart LNM for AIX. |
| 2129 | Parent with name = <name> not found for segment = <segment>
in <function>. File = <filename>, Line = <line
number>
Meaning: The bridge application detected an error while cleaning up. Action: Stop LAN Network Manager, use SMIT to clear the LAN Network Manager databases, then restart LAN Network Manager. |
| 2130 | Error removing element from the list in <function>.
File
= <filename>, Line = <line number>
Meaning: The bridge application detected an error while cleaning up. Action: Stop LAN Network Manager, use SMIT to clear the LAN Network Manager databases, then restart LAN Network Manager. |
| 2134 | Cannot discover agent due to an SNMP timeout. IP Address =
<IP
address> File = <filename>, Line = <line number>
Meaning: An SNMP timeout has occurred while attempting to discover or poll the bridge. The bridge will be placed in the undiscovered subnet. Action: Verify that the agent is up and that you can retrieve attributes using the MIB browser. If so, attempt to poll the bridge. If you still receive timeout messages, change the SNMP timeout parameters in NetView/6000. |
| 2135 | Socket connection not yet established from <executable> to
<executable>.
File = <filename>, Line = <line number>
Meaning: The timer has not started yet. Action: The bridge application will wait 60 seconds and retry. |
| 2137 | Bridges with same designated bridge and designated port, but
with different segment numbers in <function>. resourceNames
= <name>
and <name>. File = <filename>, Line = <line
number>
Meaning: The bridge has detected a very unusual configuration. The IP Address of the bridges involved are located in the resource names. This may be a configuration error, or it could be caused by a bridge reporting invalid values. Action: Verify your segment numbers in the bridge configuration. |
| 2138 | Attempting to create the same bridge with different IP address.
IP Address = <IP address> File = <filename>, Line =
<line
number>
Meaning: Most bridges allow multiple IP Address to be configured for the same agent. The bridge application will verify the baseBridgeAddress to prevent the same bridge from being discover twice from two different IP addresses. Action: Remove the duplicate agent IP address using SMIT. |
| 2139 | Attempting to make another shutdown when the application is already
in the shutdown state. File = <filename>, Line = <line
number>
Meaning: The bridge application will continue to shutdown. The request is ignored. Action: None. |
| 2141 | The trap session has been closed. IP Address = <IP
address>
File = <filename>, Line = <line number>
Meaning: An error has been encountered with opening and closing the SNMP traps session. Action: Verify that the NetView/6000 trap daemons are up. Stop and restart LNM for AIX. |
| 2143 | Invalid spanning tree configuration in <name>, for
resource=<name>,
segment number=<value>, File=<file name>, line=<line number>
Meaning: The bridge has detected a very unusual configuration. This may be a configuration error, or it could be caused by a bridge reporting some invalid values. Action: Verify the spanning tree configuration for the ports connected to the segment with the specified segment number. |
| 2144 | EUI resynchronize failed. Return Code=<value>, IP
address=<IP
address>
Meaning: Resynchronize requested by the user failed Action: If the problem persists, stop and restart LNM for AIX. |
| 2201 | Topology Connection error, rc = <TopoReturnCode>
Meaning: Application exits due a topology connection error. Action: Run cmlstatus to verify whether lnmtopod is running. If it is running check the nettl log and correct any problems found. If it is not running, restart LNM for AIX. If the problem persists, contact IBM Service for more information. |
| 2202 | Topology error changing station status, rc = <TopoReturnCode>,
resource = <StationName>
Meaning: An error occurred on changeResourceStatus topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2203 | Topology error changing station extension, rc = <TopoReturnCode>,
resource = <StationName>
Meaning: An error occurred on changeResourceExtension topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2204 | Topology error changing station label, rc = <TopoReturnCode>,
resource = <StationName>
Meaning: An error occurred on changeResourceLabel topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2205 | Topology error creating station, rc = <TopoReturnCode>, resource
= <StationName>
Meaning: An error occurred on createBoxGraph topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2206 | Topology error inserting station, rc = <TopoReturnCode>, resource
= <StationName>
Meaning: An error occurred on insertResource topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2207 | Topology error creating station (by trap), rc = <TopoReturnCode>,
resource = <StationName>
Meaning: An error occurred on createBoxGraph topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2208 | Topology error creating arc, rc = <TopoReturnCode>
Meaning: An error occurred on createArc topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2209 | Topology error creating concentrator box rc = <TopoReturnCode>,
resource = <ConcentratorName>
Meaning: An error occurred on createBoxGraph topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2210 | Topology error changing concentrator status, rc = <TopoReturnCode>,
resource = <ConcentratorName>
Meaning: An error occurred on changeResourceStatus topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2211 | Topology error changing concentrator label, rc = <TopoReturnCode>,
resource = <ConcentratorName>
Meaning: An error occurred on changeResourceLabel topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2212 | Topology error changing concentrator extension, rc =
<TopoReturnCode>,
resource = <ConcentratorName>
Meaning: An error occurred on changeResourceExtension topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2213 | Topology error deleting concentrator, rc = <TopoReturnCode>,
resource = <ConcentratorName>
Meaning: An error occurred on deleteResource topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2214 | Topology error removing concentrator, rc = <TopoReturnCode>,
resource = <ConcentratorName>
Meaning: An error occurred on removeResource topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2215 | Topology error changing segment contents, rc = <TopoReturnCode>,
resource = <SegmentName>
Meaning: An error occurred on changeViewContents topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2216 | Topology error deleting station, rc = <TopoReturnCode>, resource
= <StationName>
Meaning: An error occurred on deleteResource topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2217 | Topology error removing station, rc = <TopoReturnCode>, resource
= <StationName>
Meaning: An error occurred on removeResource topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2218 | Topology error resyncing segment, rc = <TopoReturnCode>, resource
= <SegmentName>
Meaning: An error occurred on a resynchronize topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2219 | Topology error changing segment status, rc = <TopoReturnCode>,
resource = <SegmentName>
Meaning: An error occurred on changeViewStatus topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2220 | Topology error changing segment label, rc = <TopoReturnCode>,
resource = <SegmentName>
Meaning: An error occurred on changeResourceLabel topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2221 | Topology error changing segment extension, rc = <TopoReturnCode>,
resource = <SegmentName>
Meaning: An error occurred on changeResourceExtension topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2222 | Topology error creating segment, rc = <TopoReturnCode>, resource
= <SegmentName>
Meaning: An error occurred on createView topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2223 | Topology error building segment, rc = <TopoReturnCode>, resource
= <SegmentName>
Meaning: An error occurred on viewBuilt topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2224 | Topology error deleting segment, rc = <TopoReturnCode>, resource
= <SegmentName>
Meaning: An error occurred on deleteView topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2225 | Topology error deleting Surrogate segments, rc = <TopoReturnCode>
Meaning: An error occurred on topoDeleteProtocol topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2226 | Topology error deleting RMON segments, rc = <TopoReturnCode>
Meaning: An error occurred on topoDeleteProtocol topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2227 | Topology error deleting SNMP 8230 segments, rc = <TopoReturnCode>
Meaning: An error occurred on topoDeleteProtocol topology call. Action: Take the following action depending on the <TopoReturnCode>:
If the problem persists, contact IBM Service for more information. |
| 2228 | Database internal error
Meaning: An error occurred on access of DBM. An open/read/write in the /usr/CML/databases/lnmTrsnmpData files failed. Action: Check the nettl log and correct any problems found. Then, restart LNM for AIX. If the problem is not solved, delete the /usr/CML/databases/lnmTrsnmpData.* files. Attention: If you delete these files you will lose such information as labels, access control policy, resource monitoring definitions, and location definitions for the SNMP token-ring segments. If the problem persists, contact IBM Service for more information. |
| 2237 | Database initialization error, rc = <DBMreturnCode>
Meaning: An error occurred on dbm_open call for one of the following reasons:
Action: Check the nettl log and correct any problems found. Then, restart LNM for AIX. If the problem is not solved, delete the /usr/CML/databases/lnmTrsnmpData.* files. Warning: If you delete these files you will lose such information as labels, access control policy, resource monitoring definitions, and location definitions for the SNMP token-ring segments. If the problem persists, record the <DBMreturnCode> and contact IBM Service for more information. |
| 2254 | Unsuccessful trap session open
Meaning: An error occurred when trying to open an snmp trap session. The application will retry to open the session. Action: Verify the SNMP configuration file (community name, etc.) |
| 2255 | Trap received for a non-managed station, MAC = <Mac Address>
Meaning: The crsNaunChange trap was received but the related station (Mac Address) is not being managed. Action: Manually resynchronize to update the AIX NetView/6000 submap. Verify that the MAC is present in the network. |
| 2257 | Oid undefined for this application, oid = <oid>
Meaning: The AGENT_FOUND message was received from cmld but the OID is not valid for this application. The message will be ignored. Action: The cmld.conf file may be corrupted. Try to restore it by using smit cml .. Configure .. LNM for AIX general configuration .. Applications to be started when LNM for AIX starts. Then set SNMP Token-Ring to No, click on Do, set it back to Yes and click on Do again. Then the cmld.conf file should be restored. Execute ovstop and then ovstart to restart cmld. Then restart LNM for AIX. If the problem persists, contact IBM Service for more information. |
| 2258 | SNMP get failed due timeout, IP = <Ip Address>
Meaning: A timeout PDU was received. Action: Verify that the agent on which the problem occurred is running. If the agent is already running, increase the timeout value for the SNMP configuration using the SNMP configuration option in NetView for AIX menu bar. |
| 2260 | SNMP set error, Segment access control could not be done, segment
= <SegmentName>
Meaning: An SNMP error occurred when trying to issue the remove command for a controlled station. Action: Verify that the agent on which the problem occurred is running. If the agent is already running, use the SNMP configuration option in NetView for AIX menu bar and verify that you have set the correct community name to have write access permission. If the problem persists, contact IBM Service for more information. |
| 2261 | Surrogate station attachment error, status = <attachStatus>,
MAC = <Mac Address>
Meaning: The rpsLastAttachedReportStationInRing trap was received. The status of the attachment process indicates an error. The station was not inserted in the ring. Action: Verify that this MAC was correctly inserted in the network. |
| 2262 | The station should have been already created at this time, MAC = <Mac
Address>
Meaning: An error occurred when processing a surrogate trap. A station should have been already created when an SNMP GET response is received from the surrogate. Action: This is an unexpected condition. Resynchronizing the segment will update AIX NetView/6000. Verify that this MAC was correctly inserted in the network. |
| 2263 | REM and/or CRS functions not available for segment
<SegmentName>.
Meaning: Informative. Action: Verify whether the agent provides REM and CRS functions. Also, verify whether these functions are enabled by using the segment configuration window. |
| 2267 | SNMP GET/SET error, rc = <SNMP ErrorCode>, Segment =
<segmentName>
Meaning: A GET/SET response was received with error for one the following reasons:
Action: Verify that the agent on which the problem occurred is running. If the agent is already running, use the SNMP configuration option in NetView for AIX menu bar, and verify if you have set the correct community name to have write access permission. If the problem persists, contact IBM Service for more information. |
| 2268 | SNMP get/set/get_next failed due timeout, Segment = <Segment Name>
Meaning: A timeout PDU was received. Action: Verify that the agent on which the problem occurred is running. If the agent is already running, increase the timeout value for the SNMP configuration using the SNMP configuration option in NetView for AIX menu bar. |
| 2269 | Error sending snmp GET/SET, Segment = <Segment Name>
Meaning: A SNMP get or set request could not be sent Action: Verify that the agent on which the problem occurred is running. If the agent is already running, try to ping it. If you can ping the agent and the problem persists, contact IBM Service for more information. |
| 2270 | Management application connection error
Meaning: The application cannot communicate with lnmtrmgr. Action: Verify that lnmtrmgr is running. If it is not running, access any SNMP token-ring window and lnmtrmgr will be started. If it is running and the problem persists, contact IBM Service for more information. |
| 2275 | Application ended with error, rc = <ErrorCode>
Meaning: lnmtrmon process exits for one of the following reasons:
Action: This message can be used in conjunction with the response from cmlstatus to understand why lnmtrmon is no longer running. See the man page for cmlstatus for an explanation of the exit codes. If this message is not written in the log, lnmtrmon was terminated using SIGKILL or terminated abnormally. If lnmtrmon terminated abnormally, a core dump will probably be found in the root directory. You can determine the executable that generated a core dump by entering the following command while you are in the directory with the core image. od -c core 0x4850 | head Record the information from executing dbx with the where subcommand or t subcommand and contact IBM Service for more information. |
| 2276 | Application stopped due to cmld connection error
Meaning: There was a communication problem with cmld. Action: Check the nettl log and correct any problems found. Then, restart LNM for AIX. |
| 2277 | Application stopped due to Topology connection error
Meaning: There was a communication problem with lnmtopod. Action: Check the nettl log and correct any problems found. Then, restart LNM for AIX. |
| 2278 | Application stopped due to database initialization error.
Meaning: There was a problem during internal database initialization. Action: Check the nettl log and correct any problems found. Then, restart LNM for AIX. If the problem is not solved, delete the /usr/CML/databases/lnmTrsnmpData.* files. Warning: If you delete these files you will lose such information as labels, access control policy, resource monitoring definitions, and location definitions for the SNMP token-ring segments. If the problem persists, contact IBM Service for more information. |
| 2279 | Application stopped due to database record deletion error.
Meaning: There was a problem during internal database operation. Action: Check the nettl log and correct any problems found. Then, restart LNM for AIX. If the problem is not solved, delete the /usr/CML/databases/lnmTrsnmpData.* files. Warning: If you delete these files you will lose such information as labels, access control policy, resource monitoring definitions, and location definitions for the SNMP token-ring segments. If the problem persists, contact IBM Service for more information. |
| 2281 | Authentication failure, IP = <IP address>
Meaning: An SNMP generic trap 4 was received. Action: Verify that the community names match. |
| 2302 | Connection with discovery not established.
Meaning: lnmtrmgr has an interface with lnmtrmon process, and setting some attributes requires that this interface is up. Action: Restart LNM for AIX. |
| 2303 | OVW not running.
Meaning: If lnmtrmgr is started when NetView for AIX is not running this message is logged. Action: Start NetView for AIX. |
| 2308 | Cannot match attribute <PDF attribute name> with an oid from
MIB table.
Meaning: The Token Ring management application failed on trying to get an attribute from the MIB table. Action: Verify if the directory /usr/CML/databases contains the following files with read permission:
If the problem persists, contact IBM Service for more information. |
| 2313 | Cannot remove station. SNMP set operation failed.
Meaning: When the user tried to remove a station from a Ring with the Station Profile/Configuration window, a set operation error occurred. Action: Verify that the SNMP agent is up by using the MIB Browser and issuing set requests to the agent on which the problem occurred. This problem generally happens when a community name does not have write permission, which is required for a set operation. Use the SNMP configuration option in NetView for AIX menu bar, and verify that you have set the correct community name to have write access permission. If the problem persists, contact IBM Service for more information. |
| 2324 | Unable to initialize SNMP session for resource <resource
name>.
Meaning: The open function failed for the SNMP specific agent whose OID is included in the resource name. Action: Verify that the SNMP agent is up using the MIB browser. Check the SNMP configuration option using the NetView for AIX menu bar. Retry the operation. If the problem persists, contact IBM Service for more information. |
| 2325 | Cannot open MIB table <MIB table name>.
Meaning: Token Ring Management Application failed on trying to open one of the MIB tables. Action: Verify if the directory /usr/CML/databases contains the following files with read permission:
If the problem persists, contact IBM Service for more information. |
| 2326 | Cannot find label in OVw DB.
Meaning: The Token Ring management application failed on getting the label from NetView for AIX. Action: Exit from the AIX NetView/6000 graphical interface. Stop LNM for AIX. Clear the LNM databases using SMIT .. LNM for AIX .. Maintain .. Clear LNM for AIX databases. Restart LNM for AIX and AIX NetView/6000. If the problem persists, contact IBM Service for more information. |
| 2327 | There is no symbol associated to objectID: <OID>.
Meaning: The Token Ring management application failed on getting the symbol associated with the object described in the message field. Action: Exit from the AIX NetView/6000 graphical interface. Stop LNM for AIX. Clear the LNM databases using SMIT .. LNM for AIX .. Maintain .. Clear LNM for AIX databases. Restart LNM for AIX and AIX NetView/6000. If the problem persists, contact IBM Service for more information. |
| 2328 | OVw map not opened.
Meaning: The Token Ring management application failed on getting the submapID associated with the object selected. Action: Exit from the AIX NetView/6000 graphical interface. Stop LNM for AIX. Clear the LNM databases using SMIT .. LNM for AIX .. Maintain .. Clear LNM for AIX databases. Restart LNM for AIX and AIX NetView/6000. If the problem persists, contact IBM Service for more information. |
| 2332 | Error while deleting panel <Panel Name>.
Meaning: An internal error occurred when the Token Ring management application was deleting an open window. Action: Stop LNM for AIX and restart it. If the problem persist, contact IBM Service for more information. |
| 2333 | Cannot get resource label from OVw, for <Resource Label>.
Meaning: The Token Ring management application failed on getting the label from NetView for AIX for the specific resource. Action: Exit from the AIX NetView/6000 graphical interface. Stop LNM for AIX. Clear the LNM databases using SMIT .. LNM for AIX .. Maintain .. Clear LNM for AIX databases. Restart LNM for AIX and AIX NetView/6000. If the problem persists, contact IBM Service for more information. |
| 2334 | Memory fault error.
Meaning: A memory fault has occurred. This usually indicates a shortage of resources in the RS/6000 workstation. Action: Shut down some of the applications. Restart LNM for AIX and monitor the memory usage. You may need more memory for this workstation. If the problem persists, contact IBM Service for more information. |
| 2335 | Termination signal received.
Meaning: The lnmtrmgr process received an unexpected termination signal from operating system. Action: If kill -15 was used, this is informative only. Otherwise, check the log to verify why the termination signal was sent. If the problem persists, contact IBM Service for more information. |
| 2336 | Database internal error. rc=<DB internal error code>.
Meaning: An error occurred when the lnmtrmgr process tried to access the internal database. Action: Check the nettl log and correct any problems found. Then, restart LNM for AIX. If the problem is not solved, delete the /usr/CML/databases/lnmTrsnmpData.* files. Warning: If you delete these files you will lose such information as labels, access control policy, resource monitoring definitions, and location definitions for the SNMP token-ring segments. If the problem persists, contact IBM Service for more information. |
| 2337 | Cannot resynchronize segment. Connection with discovery not
established.
Restart LNM for AIX.
Meaning: A connection to lnmtrmon is required to resynchronize segments. Action: Restart LNM for AIX. |
| 2338 | Discovery application connection error. Socket info lost.
Meaning: lnmtrmgr process tried to connect with lnmtrmon and some socket information was lost. Action: Use cmlstop to stop LNM for AIX and restart it using cmlstart. If the problem persists, contact IBM Service for more information. |
| 2339 | Cannot update RMON Configuration Table. Some variables will not be
available.
Meaning: lnmtrmgr process failed on trying to set the RMON MIB. To set some variables in the RMON Configuration Table, you must first set the variable ringStationConfigUpdateStats. Action: Verify that the SNMP agent is up by using the MIB Browser and issuing set requests to the agent on which the problem occurred. This problem generally happens when a community name does not have write permission, which is required for a set operation. Use the SNMP configuration option in NetView for AIX menu bar, and verify that you have set the correct community name to have write access permission. If the problem persists, contact IBM Service for more information. |
| 2340 | Get Isolating Table Error.
Meaning: lnmtrmgr process failed on trying to get information from Isolating Table. Action: Verify that the SNMP agent is up by using the MIB Browser and issuing get requests to the agent on which the problem occurred. This problem generally happens when a community name does not have read permission which it must have for a get operation. If the problem persists, contact IBM Service for more information. |
| 2343 | Cannot access internal DB.
Meaning: An error occurred when the lnmtrmgr process tried to access the internal database. Action: Use cmlstop to stop LNM for AIX and restart it using cmlstart. Ensure that lnmtrmon application is up and running. If the problem persists, contact IBM Service for more information. |
| 2344 | SNMP get operation error.
Meaning: The lnmtrmgr process failed on getting a variable from the agent in which the problem occurred. Action: Verify that the SNMP agent is up by using the MIB Browser and issuing get requests to the agent on which the problem occurred. This problem generally happens when a community name does not have read permission, which is required for a get operation. If the problem persists, contact IBM Service for more information. |
| 2345 | SNMP get operation suspected.
Meaning: This error occurs when there was already an error getting a PDU variable. This indicates that the validity of remaining PDU variables cannot be assured. This messages is always displayed in conjunction with message number 2344. Action: Verify that the SNMP agent is up by using the MIB Browser and issuing get requests on the agent that the problem occurred. This problem generally happens when a community name does not have read permission, which is required for a get operation. If the problem persists, contact IBM Service for more information. |
| 2346 | SNMP get operation error - Agent timeout.
Meaning: The lnmtrmgr process failed to get a variable from the agent due to an agent time-out. Action: Verify that the agent on which the problem occurred is running. If the agent is already running, increase the time-out value for the SNMP configuration using the SNMP Configuration option in the NetView for AIX menu bar. The SNMP Token-Ring application of AIX requires that you do one of the following:
|
| 2347 | SNMP set operation error.
Meaning: The lnmtrmgr process failed to set a variable on the agent on which the problem occurred. Action: Verify that the SNMP agent is up by using the MIB Browser and issuing set requests to the agent on which the problem occurred. This problem generally happens when a community name does not have write permission, which is required for a set operation. Use the SNMP configuration option in NetView for AIX menu bar, and verify that you have set the correct community name to have write access permission. If the problem persists, contact IBM Service for more information. |
| 2348 | SNMP set operation suspected.
Meaning: This error occurs when there was already an error on setting a PDU variable. This indicates that the validity of remaining PDU variables cannot be assured. This messages is always displayed in conjunction with message number 2347. Action: Verify that the SNMP agent is up by using the MIB Browser and issuing set requests on the agent that the problem occurred. This problem generally happens when a community name does not have a write permission, which is required for a set operation. Use the SNMP configuration option in NetView for AIX menu bar, and verify that you have set the correct community name to have write access permission. If the problem persists, contact IBM Service for more information. |
| 2349 | SNMP set operation error - Agent timeout.
Meaning: The lnmtrmgr process failed to set a variable on the agent due to time-out. Action: Verify that the SNMP agent is up by using the MIB Browser and issuing set requests to the agent on which the problem occurred. This problem generally happens when a community name does not have write permission, which is required for a set operation. Use the SNMP configuration option in NetView for AIX menu bar, and verify that you have set the correct community name to have write access permission. Also, increase the time-out value. The SNMP Token-Ring application of AIX requires that you do one of the following:
If the problem persists, contact IBM Service for more information. |
| 2350 | Cannot get resource label from OVw DB.
Meaning: The Token Ring management application failed to get the label from NetView for AIX. Action: Exit from the AIX NetView/6000 graphical interface. Stop LNM for AIX. Clear the LNM databases using SMIT .. LNM for AIX .. Maintain .. Clear LNM for AIX databases. Restart LNM for AIX and AIX NetView/6000. If the problem persists, contact IBM Service for more information. |
| 2352 | Connection with discovery not established.
Meaning: The lnmtrmgr process has an interface with lnmtrmon process, and setting attributes requires that this interface be up. Action: Restart LNM for AIX. |
| 2353 | Cannot resynchronize all segments. Connection with discovery not
established. Restart LNM for AIX.
Meaning: This message occurs when lnmtrmgr process tries to resynchronize all segments that are managed by the lnmtrmon. lnmtrmon must be running. Action: Restart LNM for AIX. |
| 2354 | Resync segment <segment name> failed.
Meaning: This message occurs when the lmntrmon application fails when trying to resynchronize a segment that it is managing. Action: None. |
| 2355 | Resync segment <segment name> has completed successfully.
Meaning: This message occurs when lnmtrmon finishes resynchronizing a segment. Action: None. |
| 2356 | Segment <segment name> not managed.
Meaning: This message occurs when lnmtrmon cannot resynchronize a segment because it is not managing it. Action: None. |
| 2357 | Resync all failed for at least one of the segments.
Meaning: This message occurs when lnmtrmon fails to resynchronize all the segments it is managing but was able to resynchronize one or more segments successfully. Action: None. |
| 2358 | Resync all segments has completed successfully.
Meaning: This message occurs when lnmtrmon finishes resynchronizing all the segments that it is managing. Action: None. |
| 2359 | Resync all segments already running.
Meaning: This message occurs when the user requests a resynchronization but one is already in progress. Action: None. |
| 2364 | Cannot update database record in dbSet call, rc=<internal database
error code>.
Meaning: An error occurred when the lnmtrmgr process tried to update a field in internal database. Action: Use cmlstop to stop LNM for AIX and restart them using cmlstart. Ensure that the lnmtrmon application is up and running. If the problem persists, contact IBM Service for more information. |
| 2366 | Access control policies for Token-Ring segments managed through RMON
agents will be implemented only during resynchronization. Segments
managed
through Surrogate and SNMP 8230 agents take effect continuously.
Meaning: This is an informative message that pertains only to RMON segments. The message is displayed when any change is made in access control. Action: None. |
| 2373 | Session opened.
Meaning: An SNMP session was successfully opened. Action: None. |
| 2374 | Unable to initialize SNMP session
Meaning: The application has tried to open an SNMP session but was unsuccessful. The CAU MIB variables were not read, and the SNMP Concentrator graphical view will not display until the application can successfully initialize the session. Action: None. The application will retry to initialize the session. |
| 2376 | MIB elements reading error.
Meaning: A get request for the static CAU MIB variables returned an error. A message dialog box is displayed to notify the user that the connection with the agent could not be established. Action: Verify that the SNMP agent is up by using the MIB Browser and issuing get requests to the agent on which the problem occurred. This problem generally happens when a community name does not have read permission, which is required for a get operation. Restart the agent if necessary. If the problem persists, contact IBM Service for more information. |
| 2386 | The variable cauNumberOfLobes is not consistent with the number of
lobes returned from the lobe table.
Meaning: An inconsistency was detected while getting the cauLobe table variables: for at least one module, the number of entries in the cauLobe table does not match the value of the variable cauNumberOfLobes. Action: Consult the agent documentation for how to resolve this. xnmbrowser may be useful in determining in which module(s) the error occurred. |
| 2387 | Error while getting static variables from the MIB.
Meaning: A concentrator agent communication problem (time-out) occurred while getting static variables from cau group, cauBeacon group, or MIB-II. Action: Verify that the SNMP agent is up by pinging the SNMP 8230 concentrator. If the agent is already running, increase the time-out value for the SNMP configuration using the SNMP configuration option in NetView for AIX menu bar. Restart the agent if necessary. The SNMP Token-Ring application of AIX requires that you do one of the following:
If the problem persists, contact IBM Service for more information. |
| 2388 | Error while getting tables from the MIB.
Meaning: A concentrator agent communication problem (time-out) occurred while getting variables from cauModule table or cauLobe table. Action: Verify that the SNMP agent is up by pinging the SNMP 8230 concentrator. If the agent is already running, increase the time-out value for the SNMP configuration using the SNMP configuration option in NetView for AIX menu bar. Restart the agent if necessary. The SNMP Token-Ring application of AIX requires that you do one of the following:
If the problem persists, contact IBM Service for more information. |
| 2502 | Socket connection from <process1> to <process2>
failed.
process1 <lnmhubint> process2 <Process name> errno
= <errnoValue> File = <File Name> Line = <Line
Number>
Meaning: The Hub Manager integration daemon (lnmhubint) lost the socket connection to another process. This message usually indicates that the other process failed and lnmhubint will terminate as a result. The error indicates the error number and the File and Line number indicates the location where the error occurred. Action: The following list describes the processes that lnmhubint communicates with and the actions that should be taken in order to recover.
If the actions recommended above do not solve the problem, check the nettl log for other error messages that may be causing the problem. Contact IBM Service if more information is needed. |
| 2503 | lnmhubint exiting Exit code = <errnoValue> File =
<File
Name> Line = <Line Number>
Meaning: lnmhubint is terminating for one of the following reasons:
Action: This message can be used in conjunction with the response from cmlstatus to understand why lnmhubint is no longer running. See the man page for cmlstatus for an explanation of the exit codes. If lnmhubint terminated abnormally, a core dump will probably be found in the root directory. You can determine the executable that generated a core dump by entering the following command while you are in the directory with the core image od -c core 0x4850 | head Record the information from executing dbx with the where subcommand or the t subcommand. Contact IBM Service for more information. |
| 2504 | Unexpected value in switch statement. Procedure
<methodName>
Switch value<value> File<File Name> Line<Line
Number>
Meaning: This message is used for any unexpected values. The Procedure will identify the type of error. The Exit code indicates the error number and the File and Line number indicates the location where the error occurred. Action:
|
| 2505 | Duplicate start message received. File = <File Name>
Line = <Line Number>
Meaning: The lnmhubint received a second start message from the LNM for AIX control program. The duplicate message will be ignored. Action: None. |